Install Enterprise Manager Console Oracle 11g
Oracle Enterprise Manager Grid Control is a tool to manage and monitor multiple instances of Oracle and non-Oracle platforms such as Microsoft.NET, Microsoft SQL Server, NetApp Filers, BEA weblogic and others. I’ll show how to install Oracle Grid Control 11g on Oracle Linux (32bit). Here are the main steps: 1) Installation of Oracle Linux () 2) Installation of Oracle Database 11.2.0.2 (Repository Database) 3) Installation of Java and Weblogic Server (Middleware) 4) Installation of Grid Control 5) Installation of Grid Control Agent to a Target System Installation of Oracle Database 11.2 After you install Oracle Linux, login as root and create the directories for Grid Control and other software we’ll install. Unzip linux_11gR2_database_2of2.zip Unzip will create a directory named “database”, go into this directory and run “./runInstaller”: I’ll not set up MOS credentials now and will do a vanilla install. Uncheck the “I wish to receive security updates” and click next.
ORACLE-BASE - Learn how to install OEM Grid Control 11gR1 on Oracle Linux 5.5 (64-bit). In this article I'll describe the installation of Oracle 11g Release 1 Grid Control on Oracle Linux (OL 5.5 64-bit). If you have performed a default installation you will need to deconfigure Enterprise Manager Database Control.
Again, I select “skip software updates” and click next. Select “create and configure a database”, click next.
Select “server class”, it will allow us more options. Select “single instance” and click next. We can go with “typical install” but I’ll select “advanced install” for more options. Select the languages you want to use (for the dialogs etc), “english” is fine.
So click next. EM Grid Control requires “Enterprise Edition”, so be sure the select the enterprise edition and click next. Enter the path for the Oracle Base. Installer will change the target path for the software location (ORACLE_HOME) according to the path for the oracle base. Enter the location for the Oracle Inventory, click next. Select “general purpose” for database type and click next. Enter the global database name (and SID), click next.
I’ll not change default settings of database bu memory usage. Because this system has only 2GB, I’ll set 500MB for database service. It’s ok to use EM Database Control for now, we’ll remove it later. So click next I’ll use file system to store datafiles, click next. I’ll not enable auto backups, you can enable if you want. Enter strong passwords (which contains upper and lower cases characters and at least one numberic character) for system users.
DBA group is ok, click next. So we’re ready to install the database, click “install”. Wait until software installation completed. When the software is installed, DBCA utility will create the database automatically. The database is created. Click OK to close the window.
Open a terminal window, switch to root user by issuing “su – root”, and run the scripts to complete the installation. Press enter to accept the default values for the script asks. After you run the both scripts, click OK. Database installation is completed, now we need to some changes to be able to use this database as Grid Control repository. Let’s set the environment variables to be able to connect the database (or you can create unix profile script and use it: ). Emctl stop dbconsole Oracle Enterprise Manager 11g Database Control Release 11.2.0.2.0 Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Stopping Oracle Enterprise Manager 11g Database Control. Emca -deconfig dbcontrol db -repos drop STARTED EMCA at Jul 21, 2011 2:17:39 PM EM Configuration Assistant, Version 11.2.0.0.2 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: emrep Listener port number: 1521 Password for SYS user: Password for SYSMAN user: ---------------------------------------------------------------------- WARNING: While repository is dropped the database will be put in quiesce mode.
---------------------------------------------------------------------- Do you wish to continue? [yes(Y)/no(N)]: y Jul 21, 2011 2:18:08 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /u01/oracle/cfgtoollogs/emca/emrep/emca_2011_07_21.log. Jul 21, 2011 2:18:08 PM oracle.sysman.emcp.util.DBControlUtil stopOMS INFO: Stopping Database Control (this may take a while).
Jul 21, 2011 2:18:09 PM oracle.sysman.emcp.EMReposConfig invoke INFO: Dropping the EM repository (this may take a while). Do you wish to continue? [yes(Y)/no(N)]: y Jul 21, 2011 2:18:08 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /u01/oracle/cfgtoollogs/emca/emrep/emca_2011_07_21.log. Jul 21, 2011 2:18:08 PM oracle.sysman.emcp.util.DBControlUtil stopOMS INFO: Stopping Database Control (this may take a while). Jul 21, 2011 2:18:09 PM oracle.sysman.emcp.EMReposConfig invoke INFO: Dropping the EM repository (this may take a while).
Jul 21, 2011 2:21:28 PM oracle.sysman.emcp.EMReposConfig invoke INFO: Repository successfully dropped Enterprise Manager configuration completed successfully FINISHED EMCA at Jul 21, 2011 2:21:30 PM. ALTER DATABASE DATAFILE '/u01/oracle/oradata/emrep/undotbs01.dbf' RESIZE 200M; We restart the database for settings take effect. Installation of Java and Weblogic Server It’s time to install Weblogic Application Server, but before installing Weblogic Application Server, we need to install (update) our Java to 1.6.x: We should download and install 10.3.2 version from Oracle: 32bit Linux version (I’ll use this one): If you’ll install 64bit, be sure that you install 64bit version of Java SDK and install the generic version: You can start 64bit install for Weblogic Server by issuing the following command. Java -d64 -jar wls1032_generic.jar This is welcome screen, click next. Enter the path for the middleware home (a folder that can accessed by oracle) and click next. I do not wish the security updates, so uncheck the box and click next. Select the typical installation, and click next.
You can accept the default value for the weblogic server path, click next. Wait until the installation completed. Uncheck the “run quickstart” and click done to complete the installation. Installation of Grid Control Ok so we have a database (ready for being repository for Grid Control) and weblogic server. Now it’s time to install the Grid Control.
Download the Grid Control zip files from Oracle: Here are the links for Linux 32bit version: unzip the files then go into “grid” and run the installer. ./runInstaller As I said, I’ll make a vailla install so I will not enter the MOS credentials. I uncheck the box for “I wish to receive security updates” and accept the dialog and click next. Select skip software updates and click next. Select “new install” and click next If you have followed my documents from the start (including installation of OS), all prerequisites should have been satisfied. Accept the default values and click next. Enter the passwords for weblogic user and node manager.
Enter the connection details for the repository database, when you click next, Installer will check the information and warn you if any error occurs. Enter the password for user SYSMAN. Grid Control data will be stored in SYSMAN schema. Default paths are OK for me, so I will not change the default paths of the new datafiles. Enter the registration password. Grid Agents will register to Grid Control service by using this password. You can disable HTTP (insecure) connections to your service and web interface.
I’ll leave the boxes checked so all communion will be secure. You can change the ports but I recommend you to accept the defaults and click next. Click “install” to start installing Grid Control software.
Wait until installation completed. Open a terminal, switch to root (su -) and run the root script, then click OK. Wait until the installer configures your Grid Control. Installation completed.
Now we can read the Grid Control: Because Grid Control do not use a valid SSL certificate, you’ll get a warning when you try to connect. Ignore the warning (accept the risk) and proceed to the website. When it asks for the username and password, you should enter the password of SYSMAN. Installation of Grid Control Agent to a Target System As you know, Grid Control is designed to manage and monitor multiple databases, now I’ll install the grid control agent to another server (running on Oracle Linux 5.6 32bit).
Oracle 10g installed on the target server. Because our Grid Control and target server have the same Operation system and architecture, I will not download additional agent software. Go to deployment page, click “install agent” under the title Agent Installation. Click “Fresh install” Enter the installation details. You must enter: 1) Select the platform (architecture of the target system); 2) Host name into “host list” (you can start installing agents to multiple targets); 3) OS Credientals – uncheck the run root.sh unless the user has sudo privileges; 4) Installation base directory (this is in target server); 5) Management Server Registration Password Before click continue, edit /etc/hosts files of both target and Grid Control server and add the hostnames and IPs.
My grid control server’s name is oelgrid11.gokhanatil.com and name of the target server is ora10lin.gokhanatil.com. I add the following line to /etc/hosts of target server: 192.168.100.101 oelgrid11.gokhanatil.com I also add the following line to /etc/hosts of Grid Control: 192.168.100.105 ora10lin.gokhanatil.com So both servers can resolve the host names of each other. You can try to ping each other to be sure. Uncheck the box about security updates or enter the MOS credentials, click “submit”. Click yes to continue. Wait until agent is installed (it may take some time). Our target server is registered to Grid Control.
Connect to the target server, login as root and run the root.sh file: /root.sh (for example: /u01/oracle/agent11/root.sh) We can see the target server on the hosts page. Although we can see the database of the new server, we need to configure it so Grid Control can monitor it. Select the database, and then click “configure”. DBSNMP will be used to monitor the database.
If this is a new database, enter a dummy password for user DBSNMP and click “test connection”. As you see, Grid Control will ask you if you want to change the password of DBSNMP. Click “change dbsnmp password” button. Enter the password of system (or any other user which can unlock and change password of dbsnmp) and a new password for dbsnmp, then click OK. Now password of dbsnmp has been changed, click next.
If your target database is 10g or higher, then it will go to last step. If your target database is 9i, it will ask you some questions about installing statspack. Click “submit” to complete the configuration. Our target server and the database running on that server registered to Grid Control and required configuration is done.
Hi Gokhan, Thanks for the great post. But I stucked on OMS Configuration step. I used the same weblogic and gridcontrol version as you did. Here is the error log: Thu Jan 17 15:29:24 CST 2013 Admin server started successfully.
Disconnected from weblogic server: EMGC_ADMINSERVER Thu Jan 17 15:29:24 CST 2013 Done: Starting Admin Server You will need to be connected to a running server to execute this command Jan 17, 2013 3:29:25 PM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand INFO: error messages of the command: weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at oel655v151:7,403.
At java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl. Nursing Informatics And The Foundation Of Knowledge Ebook Reader here. connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) Could you give me any clue on this problem? Hi Gokhan, Thanks for this wonderful post!!
I actually stumbled on your blog while looking for a documentation on how to install Grid control on Windows xp. I just resumed on a project where the environment is purely windows. (I must confess am finding it hard to get use to it since I have a 2 node RAC on RHEL 5 I built at home and my last env was purely UNIX (AIX & Solaris). I have a spare server at home and I really would love to know: 1. If I can add the above config to my lab env cos i plan to have a full env for practice. How can I install Grid control 11 on windows xp?
Thanks for your swift response Prince. Hi Gokhan, I need to download the EM Oracle Grid Control 11g for Windows 64 bits. When i go to the link:, in the “Previous Enterprise Manager Release Software” there is a paragraph “Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) Enterprise Manager Grid Control 11g is no longer available for download. The software is available as a media request for those customers who own a valid Enterprise Manager product license purchased prior to September 30, 2012. To request access to the media, follow Note.1071023.1 from My Oracle Support. ” but this note gives a links to download compressed patches and many of them failed to be downloaded.
So, please provide the link to download EM Oracle Grid Control 11g for Windows 64 bits. Many thanks and best regards. Hi Gokhan, Good post. Thankful to you for providing such a good document. I have installed Grid Control 11g in my VM and repository database version is 11.2.0.3.0its working fine no issues in that. I mainly used Grid becuase I want to have all the DB server alter,log,error,issues centrally.
Also I want to generate customized report like Active usage of any DB instance or etc. I try to create report but always failed with either table/view does not exists or some unnkow error. I used SQL from different view like V$session etc Can you help us to create custom report or provide me some learing link through which I can help my self to generate reports I want. Thanks again. Connecting to Node Manager This Exception occurred at Wed Sep 17 09:21:18 AST 2014. Weblogic.nodemanager.NMException: Configuration error while reading domain directory Wed Sep 17 09:21:18 AST 2014 SEVERE: Exception: during stop of admin server Wed Sep 17 09:21:18 AST 2014 Name of Exception: main.WLSTException Wed Sep 17 09:21:18 AST 2014 Code of Exception: Error occured while performing nmConnect: Cannot connect to Node Manager.: Configuration error while reading domain directory Use dumpStack() to view the full stacktrace Wed Sep 17 09:21:18 AST 2014 Connecting to Node Manager This Exception occurred at Wed Sep 17 09:21:18 AST 2014.
OMS service failed with errors. Code of Exception: Error occured while performing nmConnect: Cannot connect to Node Manager.: Configuration error while reading domain directory Use dumpStack() to view the full stacktrace Sun Feb 15 02:36:50 IST 2015 Connecting to Node Manager This Exception occurred at Sun Feb 15 02:36:50 IST 2015.
Weblogic.nodemanager.NMException: Configuration error while reading domain directory Sun Feb 15 02:36:50 IST 2015 SEVERE: Exception: during stop of admin server Sun Feb 15 02:36:50 IST 2015 Name of Exception: main.WLSTException Sun Feb 15 02:36:50 IST 2015 Code of Exception: Error occured while performing nmConnect: Cannot connect to Node Manager.: Configuration error while reading domain directory Use dumpStack() to view the full stacktrace Sun Feb 15 02:36:50 IST 2015 Connecting to Node Manager This Exception occurred at Sun Feb 15 02:36:50 IST 2015. Gokhan: Your step by step instructions are always helpful and handy. However, I have a few questions. Perhaps you know and deal with oracle servers and webservers so much that it is kind of become murky for the occasional DBA’s. The Oracle database is on a Linux server – this is the database server. The DBA console (EM) is on a laptop (Windows) Can you tell what software goes on what?
This is always the confusing part of all discussions. My question is, to launch Oracle Enterprisemanager from my Win Laptop, what do I have to install on each, and how to configure the apps. If you can explain this in single paragraph, that will be extremely helpful, and clear up the rest.
Oracle documentation is just about as bad as the IBM documentation of the 1970’s, and I am an old vintage from that era. Hi Sivadasan, Enterprise Manager Grid/Cloud Control has 4 components: Oracle Management Service (OMS),the repository DB, EM agent and the software library. Canon Ir3245 Drivers Windows Xp. OMS is the heart of Enterprise Manager, it’s a Java application running on a weblogic server. The software library is the storage used for plugins, patches and all other applications which will be used for provisioning etc. So you’ll need an application server for these three components. The repository DB is used by OMS to store both metadata and metric data.
So EM Grid/Cloud Control requires an Oracle database to be able to run. The repository database can be located in a different server or the same server. The EM agent is the software you need to deploy to target systems. The EM agent enables you to monitor targets (such as databases, application servers etc). Hope it helps. Hi Gokhan, We are trying to install the OEM Agent on CentOS 6.5 and it is failing the below errors. You may have selected the wrong platform “Linux x86-64” for this host.
If so select the correct platform. You may have specified a non writable location for the environment variable TMP/TEMP in your shell initialization script($HOME/.cshrc, $HOME/.bashrc etc). Ensure that this location is writable.
/tmp/sfx_VHobLl/oracle.jdk/jdk/bin/java sh: /tmp/sfx_VHobLl/oracle.jdk/jdk/bin/java: Permission denied We tried with custom temp and java paths with 777 permissions too.