Installing Oracle Enterprise Manager Grid Control 11gR1 on Linux
This document will detail the installation of Oracle Enterprise Manager Grid Control 11gR1 on Oracle Enterprise Linux 5.5.
Oracle WebLogic Server 10.3.2 is required to be installed on the host in which you are going to install Enterprise Manager Grid Control. See the post Installing Oracle Weblogic Server 11g Release 1 (10.3.3) on Linux if you do not already have WebLogic Server installed. Note you cannot use Oracle Weblogic SOA Suite for Grid Control.
Note: The documentation states that Weblogic 10.3.2 or higher can be used but you may run into problems using using Weblogic Server 10.3.3 or higher. See Oracle Support Note: 1135493.1.
The Oracle Database for the repository needs to be Oracle Database 10gR2 (10.2.0.4) or higher. The UNDO table space must have at least 200MB allocated at the time of install. The parameter
SESSION_CACHED_CURSORS must be 200 or greater and the parameter
PROCESSES must be 500 or greater. If these parameters along with the
UNDO table space size are not set at the time of installation they will produce errors on Step 7 Connect to Oracle Database. If the database was created with Database Control enabled you will need to remove the Database Control repository.
To start the installation process execute the
Enter your My Oracle Support user name and password to set up security update notification and initiate configuration manager. This information is option. Click the Next button to continue.
It is possible to install patches/updates during the installation process. If you choose to apply patches/updates you can either get them on demand using your My Oracle Support login credentials or you can download the patches/updates prior to installation and store them in a central location. After making your choices click the Next button to continue.
You can either install a new Enterprise Manager system or add an addition management server. Both install options require an existing certified Oracle WebLogic server. For this document we are going to install a new Enterprise Manager system. Click the Next button to continue.
Next are the standard prerequisite checks that are common with Oracle software installs. Click the Next button to continue.
The installer should pickup the location of the middleware home that was used for the installation of Oracle WebLogic Server. If the installer does not find middleware home either type in or browse to the location that contains the Oracle WebLogic Server. You can also provide another location for the Oracle Management Service. Click the Next button to continue.
The installation process will create a WebLogic domain called GCDomain all that we need to provide is the password. Click the Next button to continue.
Now we need to provide the install the connection information for the database to be used as the repository. Provide the hostname, port, SID and SYS password for the database you are going to use for the Grid Control Repository. Click the Next button to continue.
Three table spaces are created to house the Enterprise Manager Grid Control repository. You can either accept the defaults for the data files or provide names that match your naming scheme. You also need to provide a password for the
Enter the password to be used to secure the communications between the agents and management service. You can also choose to only allow secure agents to communicate with the repository and to only allow secure access to the console. Both are set by default.
You have the ability to customize the ports used by Enterprise Manager to fit in your environment. Click the Next button to continue.
The Review screen is your last chance to make any changes to previous steps before starting the installation. Click the Install button to start the installation.
Installation steps and progress are displayed on the Install Progress screen.
At the end of the installation you will be asked to run a configuration script as the root user. In a terminal session connect as the root user and run
MW_HOME/weblogic/oms11g/allroot.sh. Note I chose not to overwrite any files.
[root@gc ~]# /u02/app/oracle/product/weblogic/oms11g/allroot.sh Starting to execute allroot.sh ......... Starting to execute /u02/app/oracle/product/weblogic/oms11g/root.sh ...... Running Oracle 11g root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /u02/app/oracle/product/weblogic/oms11g Enter the full pathname of the local bin directory: [/usr/local/bin]: The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. Adding entry to /etc/oratab file... Finished execution of /u02/app/oracle/product/weblogic/oms11g/root.sh ...... Starting to execute /u02/app/oracle/product/weblogic/agent11g/root.sh ...... Running Oracle 11g root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /u02/app/oracle/product/weblogic/agent11g Enter the full pathname of the local bin directory: [/usr/local/bin]: The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]: Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. Finished product-specific root actions. Adding entry to /etc/oratab file... Finished execution of /u02/app/oracle/product/weblogic/agent11g/root.sh ...... [root@gc ~]#
After the scripts are complete click the OK button to continue.
Next several configuration assistants will be executed.
After the entire configuration is complete you will get the Finish dialog that will detail the installation and provide the URL to access Enterprise Manager Grid Control.
Step 7 of 13 Connect to Oracle Database
If the database you are going to use as a repository is configured with Database Control you will receive an error message like the one below.
If you do get this error, click the OK button to dismiss the error and open another terminal session and run the
$ORACLE_HOME/bin/emca – deconfig dbcontrol db command. Note: If your repository database is in a RAC cluster you will need to add
[oracle@gc ~]$ emca -deconfig dbcontrol db -repos drop -SYS_PWD password -SYSMAN_PWD password STARTED EMCA at May 10, 2010 10:57:13 AM EM Configuration Assistant, Version 22.214.171.124.2 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: gcrepo Listener port number: 1521 Do you wish to continue? [yes(Y)/no(N)]: Y May 10, 2010 10:57:42 AM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /u02/app/oracle/cfgtoollogs/emca/gcrepo/emca_2010_05_10_10_57_12.log. May 10, 2010 10:57:42 AM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration WARNING: EM is not configured for this database. No EM-specific actions can be performed. May 10, 2010 10:57:42 AM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl WARNING: Error initializing SQL connection. SQL operations cannot be performed May 10, 2010 10:57:42 AM oracle.sysman.emcp.EMReposConfig invoke INFO: Dropping the EM repository (this may take a while) ... May 10, 2010 11:01:57 AM oracle.sysman.emcp.EMReposConfig invoke INFO: Repository successfully dropped Enterprise Manager configuration completed successfully FINISHED EMCA at May 10, 2010 11:01:57 AM [oracle@gc ~]$
After removing database control from the database you may receive another error such as the one below.
The database to be used as the Grid Control repository needs to have the parameters
SESSION_CACHED_CURSORS set to 200 or greater and
PROCESSES set to 500 or greater. Setting these parameters will require the database to be bounced in order for the changes to take effect. Click the OK button to dismiss the error and connect to the database to change the parameters.
SQL> alter system set session_cached_cursors=200 scope=spfile; System altered. SQL> alter system set processes=500 scope=spfile; System altered. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 1272213504 bytes Fixed Size 1336260 bytes Variable Size 771755068 bytes Database Buffers 486539264 bytes Redo Buffers 12582912 bytes Database mounted. Database opened. SQL>
If the UNDO table space does not have 200MB or more already allocated you could receive the error below.
Click the OK button to dismiss the error and resize the data file associated with the undo table space to 200MB or more.
SQL> select file_name from dba_data_files; FILE_NAME -------------------------------------------------------------------------------- /u02/app/oracle/oradata/gcrepo/users01.dbf /u02/app/oracle/oradata/gcrepo/undotbs01.dbf /u02/app/oracle/oradata/gcrepo/sysaux01.dbf /u02/app/oracle/oradata/gcrepo/system01.dbf SQL> alter database datafile '/u02/app/oracle/oradata/gcrepo/undotbs01.dbf' 2 resize 300M; Database altered. SQL>