8 Installing Enterprise Manager Grid Control

Check Database Initialization Parameters

The initialization parameters must be set correctly for your certified existing Oracle Database Enterprise Edition, to be able to create a Management Repository. You should also set all fixed parameters for your Management Repository database.

After making the changes, you must shut down and restart the database.

Fixed Initialization Parameter Values

The following table lists the parameters and their fixed values that must be met for successful Management Repository database creation. These parameters are verified by Oracle Universal Installer prerequisite checks during installation.

^Footnote 1 The TEMP space is an initialization parameter only when you are performing a Grid Control installation using a new database.

Variable Initialization Parameter Values

The variable parameter setting values are based on the size of the Grid Control environment. For the sake of clarity, the environment has been categorized as Small, Medium, and Large based on the number of targets in the environment, where:

• Small = Approximately 100 monitored targets

• Medium = Approximately 1000 monitored targets

• Large = 10000 or more monitored targets

Table 8-10 lists the variable parameter setting values.

Configuration Assistant

During the installation process, if the SYSMAN schema already exists in the database that you specify for the Management Repository, the installer will prompt you to manually drop the schema. If this is not done, the installer will automatically drop the schema before proceeding to the next configuration assistant.

If the Oracle Management Service Configuration Assistant fails before completion, you can click Retry, which automatically cleans up the repository when the configuration tool is rerun. To manually clean up the repository, use the following command:

OMS_HOME/sysman/admin/emdrep/bin/RepManager <Host name> <Port> <SID> -ACTION Drop

You may need to set the LD_LIBRARY_PATH to the ORACLE_HOME/lib directory of the OMS before running the script.

Refer to Oracle Enterprise Manager Advanced Configuration for further instructions on how to drop the existing repository from the database.

Using the Same User Name, UID, and GID

If you are installing an additional OMS on another host that will access the same, shared Oracle Software Library as the one used by the first OMS on the first host then ensure that you install the additional OMS using the same user name as the one used on the first host. Also ensure that you use the same uid and gid. This is to ensure that both the OMSes have access to the same Oracle Software Library.

Setting UID and GID Before Installing an Additional OMS

To use the same uid and gid, do these before installing the additional OMS:

1. Run the "id" command to check the uid and gid on both the computers, one where OMS is already installed and another where you are going to install the additional OMS.

2. Decide on which computer the uid and gid need to be changed. On that computer, run the following commands to open the /etc/passwd file as root:

   sudo -s
   vi /etc/passwd
   

3. Set the uid (third column) and gid (fourth column) as the ones used in the first computer.

4. Save the file.

5. Open a new terminal, login as root, and run the following command to change the ownership of the directories:

   chown <username>:<groupname> -R <directory name>
   

6. Open a new terminal, login as the OMS user, and run the "id" command to verify that the uid and gui have changed.

7. If the changes are reflected, you can start the installation of the additional OMS.

Setting UID and GID After Installing an Additional OMS

If you have already installed the additional OMS on the second computer before making the UID and GID settings, then do these:

1. Run the "id" command to check the uid and gid on both the computers where OMS is already.

2. Decide on which computer the uid and gid need to be changed. On that computer, stop or kill all the OMS-related processes.

3. Run the following commands to open the /etc/passwd file as root:

   sudo -s
   vi /etc/passwd
   

4. Change the uid (third column) and gid (fourth column) as the ones used in the first computer.

5. Save the file.

6. Now logout from the OMS that is running on this computer and re-login to ensure that the changes are reflected.

7. Open a new terminal, login as root, navigate to the OMS ORACLE_HOME (for example, /scratch/oms10203), and run the following command to change the ownership of the directories:

   chown <username>:<groupname> -R <directory name>
   

8. Open a new terminal, login as the OMS user, and run the "id" command again to verify that the uid and gui have changed.

9. In parallel, open a new terminal and access the other computer where the first OMS and the shared Oracle Software Library are present. Login to the first OMS as root and navigate to the shared Oracle Software Library directory.

   For example, if you the shared location is /net/OMS1/scratch/swlib, then run the following command:

   cd /scratch/swlib
   

10. Run the following commands to change the ownership of this shared Oracle Software Library directory:

    chown <username>:<groupname> -R <software library directory>
    

11. Now return to the second computer where the additional OMS is installed and start all the OMS-related processes that you had stopped.

Installing Enterprise Manager Grid Control Using a New Database

To install Grid Control using a new database, follow these steps:

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

2. Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:

   For UNIX Platforms:

   ./runInstaller -noconfig -silent -responseFile <absolute_path>/em_with_new_db.rsp -force

   For Microsoft Windows Platforms:

   setup.exe -noconfig -silent -responseFile <absolute_path>/em_with_new_db.rsp -force

   Note:

   • The em_with_new_db.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using a New Database of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".

   • If you want to specify different passwords for the database accounts, then ensure that the following entry is added to the em_with_new_db.rsp file:

     sl_superAdminUsers={ "SYS" , "SYSTEM" , "SYSMAN" , "DBSNMP" }

   • Use the -force command only when you want to install in an existing, nonempty directory.

3. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the following scripts on the host where you installed the base release of Grid Control.

   • If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the Central Inventory:

     $ORACLE_HOME/oraInventory/oraInstRoot.sh

   • Run the allroot.sh script from the Oracle home directory of the database (for example, db10g):

     $<ORACLE_HOME>/allroot.sh

4. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

5. Apply 10.2.0.4 or higher patch set to OMS:

   Note:

   You can download the 10.2.0.4 or higher patch set from the following location:

   http://www.oracle.com/technology/software/products/oem/index.html

   For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.

   1. Copy the patchset.rsp file from the <Patchset_Download_Location>/response/ directory to a location on your host.

   2. Edit the patchset.rsp file and make the following changes:

      For 10.2.0.4.0 Release:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      

      For 10.2.0.5.0 or Higher Release:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
      

      Note:

      • The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

      • The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

        oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

   3. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

      ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force

      Note:

      Use the -force command only when you want to install in an existing, nonempty directory.

6. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

7. Apply 10.2.0.4 or higher patch set to the Management Agent:

   1. Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.

   2. Edit the patchset.rsp file and make the following changes:

      ORACLE_HOME = <full_path_to_Oracle_home_of_Agent>
      

   3. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

      ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force

      Note:

      Use the -force command only when you want to install in an existing, nonempty directory.

8. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

9. (For Solaris Platforms Only), check the platform ID in the following file of the Oracle home directory of the database (for example, db10g). Ensure that the platform ID is set to 23. If it is not, then change it to 23.

   $<ORACLE_HOME>Inventory/ContentsXML/oraclehomeproperties.xml

10. Apply the interim RDBMS patch# 4329444 to the Oracle home directory of the database (for example, db10g) that houses the Management Repository.

11. (ONLY FOR 10.2.0.4.0 RELEASE) Apply patch# 7040389 to the Oracle home directory of the OMS (for example, oms10g).

12. Ensure that the runConfig.sh file in the Oracle home directory of the database (for example, db10g) has 'execute' permission.

    $<ORACLE_HOME>/oui/bin/runConfig.sh

13. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the environment variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

14. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

15. After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command from the Oracle home directory of the OMS:

    emctl secure unlock -console

16. If the script fails, then review the database configuration log file. The database configuration log file is available in <DB_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:

    The installer has detected that there are background dbms jobs currently running in the Repository Database. 
    

    Note:

    For Agent configuration logs, go to <AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For OMS configuration logs, go to <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw.

    If you see the error message, then before upgrading the Management Repository, do the following:

    1. Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:

       SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;

    2. Stop and restart the database.

    3. Check the status of SYSMAN user account:

       - Log in to SQLPlus as SYSDBA and run the following query:

       select username,account_status from dba_users;

       - Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:

       alter user SYSMAN account unlock;

       - Commit the changes by running the following command:

       commit;

    4. Rerun the ConfigureGC.pl script.

    5. After installation is complete, restart the DBMS jobs by running the following commands, one after the other:

       SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;

       SQL> commit;

Installing Enterprise Manager Grid Control Using an Existing Database

To install Grid Control using an existing database, follow these steps:

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

2. If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.

   To deconfigure Database Control for a single instance database, run the following command from the Oracle home directory of the database (for example, db10g):

   $<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop

   To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command from the Oracle home directory of the database (for example, db10g):

   $<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster

   After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:

   <ORACLE_HOME>/rdbms/admin/dbmspool.sql

   <ORACLE_HOME>rdbms/admin/prvtpool.plb

   Note:

   The command drops all the public synonyms starting with the following names created by any user for any schema:

   • 'MGMT$%'

   • 'MGMT_%'

   • 'SMP_EMD%'

   • 'SMP_MGMT%'

   • 'SETEMVIEWUSERCONTEXT'

   • 'DBMS_SHARED_POOL'

   • 'EMD_MNTR'

   • 'ECM_UTIL'

3. Ensure that the database initialization parameters have the correct values to create a Management Repository in the database.

   For information about the initialization parameters to be edited and the values to be provided, see Check Database Initialization Parameters.

   Note:

   If you do not set the database initialization parameters, the installation will fail and you will find the error message "OUI-10155:Error" in the following log file:

   <DB_HOME>/cfgtoollogs/cfgfw/installActions<time_stamp>.log

   To resolve it, set the parameters with correct values as given in Check Database Initialization Parameters, deinstall the failed Oracle homes, and then restart the installation.

4. Log in to the database as SYSDBA and run the following command:

   @?/rdbms/admin/dbmspool.sql

   commit;

5. Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:

   For UNIX Platforms:

   ./runInstaller -noconfig -silent -responseFile <absolute_path>/em_using_existing_db.rsp -force

   For Microsoft Windows Platforms:

   setup.exe -noconfig -silent -responseFile <absolute_path>/em_using_existing_db.rsp -force

   Note:

   • The em_using_existing_db.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".

   • Use the -force command only when you want to install in an existing, nonempty directory.

6. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

7. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/allroot.sh

8. Apply 10.2.0.4 or higher patch set to OMS:

   Note:

   You can download the 10.2.0.4 or higher patch set from the following location:

   http://www.oracle.com/technology/software/products/oem/index.html

   For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.

   1. Copy the patchset.rsp file from the <Patchset_Downloaded_Location>/response/ directory to a location on your host.

   2. Edit the patchset.rsp file and make the following changes:

      For 10.2.0.4.0 Release:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      

      For 10.2.0.5.0 or Higher Release:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
      

      Note:

      • The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

      • The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

        oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

   3. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

      ./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp

9. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

10. (ONLY FOR 10.2.0.4.0 RELEASE) Apply the following patches depending on how the database, which houses the Management Repository, is configured:

    • If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.

    • If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS

11. Apply 10.2.0.4 or higher patch set to the Management Agent:

    1. Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.

    2. Edit the patchset.rsp file and make the following changes:

       ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
       

    3. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

       ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force

       Note:

       Use the -force command only when you want to install in an existing, nonempty directory.

12. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

13. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable PERL5LIB, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

14. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

15. After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:

    emctl secure unlock -console

16. If the script fails, then look at the OMS configuration log file. The OMS configuration log file is available in <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:

    The installer has detected that there are background dbms jobs currently running in the Repository Database. 
    

    Note:

    For Agent configuration logs, go to <AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For Database configuration logs, go to <DB_ORACLE_HOME>/cfgtoollogs/cfgfw.

    If you see the error message, then before upgrading the Management Repository, do the following:

    1. Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:

       SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;

    2. Stop and restart the database.

    3. Check the status of SYSMAN user account:

       - Log in to SQLPlus as SYSDBA and run the following query:

       select username,account_status from dba_users;

       - Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:

       alter user SYSMAN account unlock;

       - Commit the changes by running the following command:

       commit;

    4. Rerun the ConfigureGC.pl script.

    5. After installation is complete, restart the DBMS jobs by running the following commands, one after the other:

       SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;

       SQL> commit;

Installing Additional Management Service

To install an additional OMS, follow these steps:

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

2. Ensure that the database, which houses the repository, and its listener are running.

3. Log in to the database as SYSDBA user and convert the repository version from 10.2.0.4.0 or higher to 10.2.0.1.0 by running the following SQL statement:

   UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;

4. Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):

   For UNIX Platforms:

   ./runInstaller -noconfig -silent -responseFile additional_mgmt_service.rsp

   For Microsoft Windows Platforms:

   setup.exe -noconfig -silent -responseFile additional_mgmt_service.rsp

   Note:

   The additional_mgmt_service.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Additional Management Service of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".

5. Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.4.0 or higher, by using the following SQL statement. The following SQL statement uses 10.2.0.4.0 as an example; therefore, it you are installing a higher release, then replace it with that release number.

   UPDATE sysman.mgmt_versions SET version = '10.2.0.4.0' where component_name='CORE'; commit;

6. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>allroot.sh

7. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

8. Apply 10.2.0.4 or higher patch set to OMS:

   Note:

   You can download the 10.2.0.4 or higher patch set from the following location:

   http://www.oracle.com/technology/software/products/oem/index.html

   For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.

   1. Copy the patchset.rsp file from the <Patchset_Downloaded_Location>/response/ directory to a location on your host.

   2. Edit the patchset.rsp file and make the following changes:

      For 10.2.0.4.0 Release:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      

      For 10.2.0.5.0 or Higher Release:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
      

      Note:

      • The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

      • The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

        oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

   3. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

      ./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp

9. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

10. Apply the following patches depending on how the database, which houses the Management Repository, is configured:

    • If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.

    • If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS

11. Apply 10.2.0.4 or higher patch set to the Management Agent:

    1. Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.

    2. Edit the patchset.rsp file and make the following changes:

       ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
       

    3. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

       ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force

       Note:

       Use the -force command only when you want to install in an existing, nonempty directory.

12. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

13. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable PERL5LIB, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

14. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

15. After the script runs successfully, Grid Control is configured to 10.2.0.4 release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:

    emctl secure unlock -console

Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Oracle Database 11g

To install Grid Control using an existing Oracle Database 11g, follow these steps:

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

2. If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.

   To deconfigure Database Control for a single instance database, run the following command from the Oracle home directory of the database (for example, db10g):

   $<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop

   To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command from the Oracle home directory of the database (for example, db10g):

   $<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster

   After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:

   <ORACLE_HOME>/rdbms/admin/dbmspool.sql

   <ORACLE_HOME>rdbms/admin/prvtpool.plb

   Note:

   The command drops all the public synonyms starting with the following names created by any user for any schema:

   • 'MGMT$%'

   • 'MGMT_%'

   • 'SMP_EMD%'

   • 'SMP_MGMT%'

   • 'SETEMVIEWUSERCONTEXT'

   • 'DBMS_SHARED_POOL'

   • 'EMD_MNTR'

   • 'ECM_UTIL'

3. Ensure that the database initialization parameters have the correct values to create a Management Repository in the database.

   For information about the initialization parameters to be edited and the values to be provided, see Check Database Initialization Parameters.

   Note:

   If you do not set the database initialization parameters, the installation will fail and you will find the error message "OUI-10155:Error" in the following log file:

   <DB_HOME>/cfgtoollogs/cfgfw/installActions<time_stamp>.log

   To resolve it, set the parameters with correct values as given in Check Database Initialization Parameters, deinstall the failed Oracle homes, and then restart the installation.

4. Log in to the database as SYSDBA and run the following command:

   @?/rdbms/admin/dbmspool.sql

   commit;

5. (ONLY FOR Oracle Enterprise Linux (OEL) 5.X and Red Hat Enterprise Linux 5.X) If /usr/lib/libdb.so.2 does not exist, then run the following command:

   ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

6. Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:

   For UNIX Platforms:

   ./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile <location of em_using_existing_db.rsp> use_prereq_checker=false b_skipDBValidation=true

   For Microsoft Windows Platforms:

   setup.exe -noconfig -ignoreSysPrereqs -silent -responseFile <location of em_using_existing_db.rsp> use_prereq_checker=false

   Note:

   The em_using_existing_db.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".

7. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

8. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/allroot.sh

9. Apply 10.2.0.5 or higher patch set to OMS:

   Note:

   You can download the 10.2.0.5 or higher patch set from the following location:

   http://www.oracle.com/technology/software/products/oem/index.html

   For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.

   1. Copy the patchset.rsp file from the <Patchset_Downloaded_Location>/response/ directory to a location on your host.

   2. Edit the patchset.rsp file and make the following changes:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
      

      Note:

      • The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

      • The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

        oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

   3. Apply 10.2.0.5 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

      ./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp

10. From the Oracle home directory of the OMS, run root.sh.

11. Apply 10.2.0.5 or higher patch set to the Management Agent:

    1. Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.

    2. Edit the patchset.rsp file and make the following changes:

       ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
       

    3. Apply 10.2.0.5 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

       ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force

       Note:

       Use the -force command only when you want to install in an existing, nonempty directory.

12. From the Oracle home directory of the Management Agent, run root.sh.

13. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable PERL5LIB, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

14. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

15. After the script runs successfully, Grid Control is configured to 10.2.0.5 or higher release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:

    emctl secure unlock -console

16. If the script fails, then look at the OMS configuration log file. The OMS configuration log file is available in <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:

    The installer has detected that there are background dbms jobs currently running in the Repository Database. 
    

    Note:

    For Agent configuration logs, go to <AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For Database configuration logs, go to <DB_ORACLE_HOME>/cfgtoollogs/cfgfw.

    If you see the error message, then before upgrading the Management Repository, do the following:

    1. Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:

       SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;

    2. Stop and restart the database.

    3. Check the status of SYSMAN user account:

       - Log in to SQLPlus as SYSDBA and run the following query:

       select username,account_status from dba_users;

       - Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:

       alter user SYSMAN account unlock;

       - Commit the changes by running the following command:

       commit;

    4. Rerun the ConfigureGC.pl script.

    5. After installation is complete, restart the DBMS jobs by running the following commands, one after the other:

       SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;

       SQL> commit;

Installing Additional Management Service Using Existing Oracle Database 11g

To install an additional OMS to connect to an existing Oracle Database 11g, follow these steps:

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

2. Ensure that the database, which houses the repository, and its listener are running.

3. Log in to the database as SYSDBA user and convert the repository version from 10.2.0.5.0 or higher to 10.2.0.1.0 by running the following SQL statement:

   UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;

4. Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):

   For UNIX Platforms:

   ./runInstaller -noconfig -silent -responseFile additional_mgmt_service.rsp use_prereq_checker=false b_skipDBValidation=true

   For Microsoft Windows Platforms:

   setup.exe -noconfig -silent -responseFile additional_mgmt_service.rsp use_prereq_checker=false

   Note:

   The additional_mgmt_service.rsp file is packaged with Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Additional Management Service of Chapter 9, "Installing Enterprise Manager Grid Control in Silent Mode".

5. Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.5.0 or higher, by using the following SQL statement. The following SQL statement uses 10.2.0.5.0 as an example; therefore, it you are installing a higher release, then replace it with that release number.

   UPDATE sysman.mgmt_versions SET version = '10.2.0.5.0' where component_name='CORE'; commit;

6. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>allroot.sh

7. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

8. Apply 10.2.0.5 or higher patch set to OMS:

   Note:

   You can download the 10.2.0.5 or higher patch set from the following location:

   http://www.oracle.com/technology/software/products/oem/index.html

   For each patch set, you might have to download either a single ZIP file or multiple ZIP files. If you have to download more than one ZIP file, then extract the contents of the ZIP files into one directory. For more information about these ZIP files and how you can extract them, see the README file associated with the patch set.

   1. Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.

   2. Edit the patchset.rsp file and make the following changes:

      b_softwareonly = true 
      s_sysPassword  = <sys user password>
      ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
      oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
      

      Note:

      • The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

      • The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

        oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

   3. Apply 10.2.0.5 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

      ./runInstaller -noconfig -silent -responseFile <exact_path>/patchset.rsp

9. From the Oracle home directory of the OMS, run root.sh.

10. Apply 10.2.0.5 or higher patch set to the Management Agent:

    1. Copy the patchset.rsp file from the <Patch Set DVD>/response/ directory to a location on your host.

    2. Edit the patchset.rsp file and make the following changes:

       ORACLE_HOME = <full_path_to_Oracle_home_of__Agent>
       

    3. Apply 10.2.0.5 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

       ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp -force

       Note:

       Use the -force command only when you want to install in an existing, nonempty directory.

11. From the Oracle home directory of the Management Agent, run root.sh.

12. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable PERL5LIB, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

13. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

14. After the script runs successfully, Grid Control is configured to 10.2.0.5 release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:

    emctl secure unlock -console

Installing Enterprise Manager Grid Control Using an Existing Database

To install Grid Control using an existing database, follow these steps:

1. If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Grid Control.

   To deconfigure Database Control for a single instance database, run the following command from the Oracle home directory of the database (for example, db10g):

   $<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop

   To deconfigure Database Control for a Real Application Clusters (RAC) database, run the following command from the Oracle home directory of the database (for example, db10g):

   $<ORACLE HOME>/bin/emca -deconfig dbcontrol db -repos drop - cluster

   After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:

   <ORACLE_HOME>/rdbms/admin/dbmspool.sql

   <ORACLE_HOME>rdbms/admin/prvtpool.plb

   Note:

   The command drops all the public synonyms starting with the following names created by any user for any schema:

   • 'MGMT$%'

   • 'MGMT_%'

   • 'SMP_EMD%'

   • 'SMP_MGMT%'

   • 'SETEMVIEWUSERCONTEXT'

   • 'DBMS_SHARED_POOL'

   • 'EMD_MNTR'

   • 'ECM_UTIL'

2. Ensure that the database initialization parameters have the correct values to create a Management Repository in the database.

   For information about the initialization parameters to be edited and the values to be provided, see Check Database Initialization Parameters.

   Note:

   If you do not set the database initialization parameters, the installation will fail and you will find the error message "OUI-10155:Error" in the following log file:

   <DB_HOME>/cfgtoollogs/cfgfw/installActions<time_stamp>.log

   To resolve it, set the parameters with correct values as given in Check Database Initialization Parameters, deinstall the failed Oracle homes, and then restart the installation.

3. Log in to the database as SYSDBA and run the following command:

   @?/rdbms/admin/dbmspool.sql

   commit;

4. Install the base release of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) using the following command:

   For UNIX Platforms:

   ./runInstaller -noconfig

   For Microsoft Windows Platforms:

   setup.exe -noconfig

5. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

6. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/allroot.sh

7. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

   ./runInstaller -noconfig b_softwareonly=true

8. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

9. (ONLY FOR 10.2.0.4.0 RELEASE) Apply the following patches depending on how the database, which houses the Management Repository, is configured:

   • If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.

   • If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS

10. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

    ./runInstaller -noconfig

11. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

12. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable PERL5LIB, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

13. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

14. After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:

    emctl secure unlock -console

15. If the script fails, then look at the OMS configuration log file. The OMS configuration log file is available in <OMS_ORACLE_HOME>/cfgtoollogs/cfgfw. Scan through the logs to see if you have the following error message:

    The installer has detected that there are background dbms jobs currently running in the Repository Database. 
    

    Note:

    For Agent configuration logs, go to <AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw. For Database configuration logs, go to <DB_ORACLE_HOME>/cfgtoollogs/cfgfw.

    If you see the error message, then before upgrading the Management Repository, do the following:

    1. Stop the running DBMS jobs by logging in to SQL as SYSDBA and running the following command:

       SQL> exec sysman.emd_maintenance.remove_em_dbms_jobs;

    2. Stop and restart the database.

    3. Check the status of SYSMAN user account:

       - Log in to SQLPlus as SYSDBA and run the following query:

       select username,account_status from dba_users;

       - Ensure that the SYSMAN user account is in 'open' status. If the account is not in open status, then run the following command:

       alter user SYSMAN account unlock;

       - Commit the changes by running the following command:

       commit;

    4. Rerun the ConfigureGC.pl script.

    5. After installation is complete, restart the DBMS jobs by running the following commands, one after the other:

       SQL> exec sysman.emd_maintenance.submit_em_dbms_jobs;

       SQL> commit;

Installing Additional Management Service

To install additional OMS, follow these steps:

1. Ensure that the database, which houses the repository, and its listener are running.

2. Log in to the database as SYSDBA user and convert the repository version from 10.2.0.4.0 or higher to 10.2.0.1.0 by running the following SQL statement:

   UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;

3. Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):

   For UNIX Platforms:

   ./runInstaller -noconfig

   For Microsoft Windows Platforms:

   setup.exe -noconfig

4. Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.4.0 or higher, by using the following SQL statement. The following SQL statement uses 10.2.0.4.0 as an example; therefore, it you are installing a higher release, then replace it with that release number.

   UPDATE sysman.mgmt_versions SET version = '10.2.0.4.0' where component_name='CORE'; commit;

5. (For UNIX Platforms Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>allroot.sh

6. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS (for example, oms10g):

   $<ORACLE_HOME>/opmn/bin/opmnctl stopall

7. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the OMS (for example, oms10g) by running the following command:

   ./runInstaller -noconfig b_softwareonly=true

8. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

9. Apply the following patches depending on how the database, which houses the Management Repository, is configured:

   • If the database is configured on a virtual host, then apply patch# 5667255 to the Oracle home directory of the OMS.

   • If the database is NOT configured on a virtual host, then apply patch# 7040389 to the Oracle home directory of the OMS

10. Apply 10.2.0.4 or higher patch set to the Oracle home directory of the Management Agent (for example, agent10g) by running the following command:

    ./runInstaller -noconfig

11. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

12. After applying the patch, make the following settings to the environment variable - PERL5LIB:

    1. Before making changes to the environment variable PERL5LIB, take a backup of the variable:

       For UNIX Platforms:

       setenv PERL5LIB_BACKUP $PERL5LIB
       

       For Microsoft Windows Platforms:

       set PERL5LIB_BACKUP=%PERL5LIB%
       

    2. Now make the following settings to the variable:

       For UNIX platforms, set it to <OMS_ORACLE_HOME>/perl/lib/5.6.1

       For Microsoft Windows platforms, set it to <OMS_ORACLE_HOME>/perl/5.6.1/lib

13. Configure Grid Control by running the ConfigureGC.pl script from the Oracle home directory of the OMS (for example, oms10g):

    For UNIX Platforms:

    $<ORACLE_HOME>/perl/bin/perl <OMS ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

    For Microsoft Windows Platforms:

    $<ORACLE_HOME>\perl\5.6.1\bin\MSWin32-x86\perl <OMS ORACLE HOME>\sysman\install\ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is C:/Program Files/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be C:/Program Files/oracle/gc.

14. After the script runs successfully, Grid Control is configured to 10.2.0.4 release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

    Note:

    For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command:

    emctl secure unlock -console

Installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) Using Existing Database

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

   Note:

   For example, if you are installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) on Red Hat Enterprise Linux 5.0, then download the full release, that is, Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) released for Linux32-bit platform. Similarly, if you are installing on HP-UX Itanium, then download the full release, that is, Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) that was released for HP-UX Itanium.

2. (ONLY FOR Oracle Enterprise Linux (OEL) 5.X and Red Hat Enterprise Linux 5.X) If /usr/lib/libdb.so.2 does not exist, then run:

   ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

3. If your existing database is configured with Database Control, then ensure that you deconfigure it before you begin the installation of Enterprise Manager Grid Control.

   To deconfigure Database Control for a single instance database, run the following command:

   $ORACLE HOME/bin/emca -deconfig dbcontrol db -repos drop

   Where $ORACLE_HOME is the Oracle home directory of existing Database.

   After deconfiguring the Database Control, connect to the database as SYS user and run the following SQL files from the Oracle home of the database:

   <ORACLE_HOME>/rdbms/admin/dbmspool.sql

   <ORACLE_HOME>rdbms/admin/prvtpool.plb

   Note:

   The command drops all the public synonyms starting with the following names created by any user for any schema:

   • 'MGMT$%'

   • 'MGMT_%'

   • 'SMP_EMD%'

   • 'SMP_MGMT%'

   • 'SETEMVIEWUSERCONTEXT'

   • 'DBMS_SHARED_POOL'

   • 'EMD_MNTR'

   • 'ECM_UTIL'

4. Verify whether all the database initialization parameters are set correctly. For information about the database initialization parameters, see Check Database Initialization Parameters.

5. Install the DBMS_SHARED_POOL package by running the below commands from the Oracle home directory of the Database:

   1. Login to the database as sysdba

   2. Run the below command:

      SQL>@?/rdbms/admin/dbmspool.sql

      SQL> commit;

6. Invoke the runInstaller:

   ./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile <location of em_using_existing_db.rsp> use_prereq_checker=false

   Note:

   The em_using_existing_db.rsp file is packaged with Enterprise Manager Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database.

7. If this is the first Oracle product you just installed on the host, then run the orainstRoot.sh script from the Central Inventory as a root user:

   $ORACLE_HOME/oraInventory/orainstRoot.sh

   Run the allroot.sh from the Oracle home of the OMS as a root user

8. Stop all OPMN processes by running the following command from the Oracle home directory of the OMS:

   $ORACLE_HOME/opmn/bin/opmnctl stopall

9. Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on your host.

   Note:

   The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

   For 10.2.0.4.0 Release:

   b_softwareonly = true
   s_sysPassword = <sys user password>
   ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
   

   For 10.2.0.5.0 or Higher Release:

   b_softwareonly = true
   s_sysPassword = <sys user password>
   ORACLE_HOME = <full_path_to_Oracle_home_of_OMS>
   oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
   

   The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. The ias_admin user is the administrative user for Oracle Application Server instances and is required for software update installation on middle-tiers.

   While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

   oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

   This password is same as the SYSMAN password that you specified when you first installed the Grid control in your environment.

   Note:

   After installing the Grid control in your environment if you change the SYSMAN password then ias_admin password will not get changed.

   To change the ias_admin password, go to the Oracle home directory of OMS and run the below command:

   $ORACLE_HOME/bin/emctl set password <Old ias_admin password> <New ias_admin Password>

   Note:

   If you don't remember the old ias_admin password then follow the instructions from Document ID 280587.1 on My Oracle Support (formerly Metalink) at http://metalink.oracle.com/

10. Apply the 10.2.0.5 patch set to the Oracle home directory of the OMS (for example, /abc/product/oms10g) by running the following command:

    ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp

11. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

12. Apply the 10.2.0.5 patch set to the Oracle home directory of the Management Agent

    • Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on yourhost.

    • Edit patchset.rsp to include the following:

      ORACLE_HOME = < Oracle home directory of the Oracle Management Agent>
      

    • Apply the 10.2.0.5 patch set to the Oracle home directory of the Management Agent:

      ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp

13. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

14. Set the PERL5LIB as <ORACLE_HOME>/perl/lib/5.6.1 where <ORACLE_HOME> is the Oracle home directory of the OMS.

15. Execute the following script from the Oracle home directory of the OMS to complete the Grid Control 10.2.0.5 install:

    $ORACLE_HOME/perl/bin/perl <ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

16. After the script runs successfully, Grid Control is configured to 10.2.0.5 or higher release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

      Note:

      For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command from the Oracle home directory of the OMS:

      emctl secure unlock -console

Installing an Additional Oracle Management Service Release 5 (10.2.0.5)

1. From the following URL, download the software for the full release of Enterprise Manager Grid Control that was release for your platform:

   http://www.oracle.com/technology/software/products/oem/index.html

   Note:

   For example, if you are installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) on Red Hat Enterprise Linux 5.0, then download the full release, that is, Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) released for Linux32-bit platform. Similarly, if you are installing on HP-UX Itanium, then download the full release, that is, Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) that was released for HP-UX Itanium.

2. (ONLY FOR Oracle Enterprise Linux (OEL) 5.X and Red Hat Enterprise Linux 5.X). If /usr/lib/libdb.so.2 does not exist, then run:

   ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

3. Ensure that the database, which houses the repository, and its listener are running.

4. Log in to the database as SYSDBA user and convert the repository version from 10.2.0.5.0 to 10.2.0.1.0 by running the following SQL statement:

   UPDATE sysman.mgmt_versions SET version = '10.2.0.1.0' where component_name='CORE'; commit;

5. Invoke the installer of Enterprise Manager 10g Grid Control Release 2 (10.2.0.1):

   ./runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile <location of additional_mgmt_service.rsp> use_prereq_checker=false b_skipDBValidation=true

   Note:

   The additional_mgmt_service.rsp file is packaged with Enterprise Manager Grid Control software. Before you run this file in silent mode, ensure that you edit the file and specify all the parameters required for a successful installation. To understand the mandatory parameters you need to specify, see Using Silent Mode to Install Additional Management Service.

6. Log in to the database again as SYSDBA user and convert the repository version back to what is was, that is, 10.2.0.5.0, by using the following SQL statement:

   UPDATE sysman.mgmt_versions SET version = '10.2.0.5.0' where component_name='CORE'; commit;

7. If this is the first Oracle product you just installed on the host, then run the orainstRoot.sh script from the Central Inventory as a root user:

   $ORACLE_HOME/oraInventory/orainstRoot.sh

8. Run the allroot.sh from the Oracle home of the OMS as a root user

9. Stop all the OPMN processes by running the following command from the Oracle home directory of the OMS:

   $ORACLE_HOME/opmn/bin/opmnctl stopall

10. Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on your host.

    Note:

    The patchset.rsp file is packaged with the Patch Set. Before editing the file, you might want to take a backup of the file to another location in order to retain the original file. Alternatively, if you want to revert to the original file, then you can always take the file from the Patch Set DVD.

    For 10.2.0.4.0 Release:

    b_softwareonly = true
    s_sysPassword = <sys user password>
    ORACLE_HOME = < full_path_to_Oracle_home_of_OMS >
    

    For 10.2.0.5.0 or Higher Release:

    b_softwareonly = true
    s_sysPassword = <sys user password>
    ORACLE_HOME = < full_path_to_Oracle_home_of_OMS >oracle.iappserver.st_midtier:szl_InstanceInformation={"ias_password"}
    

    The variable oracle.iappserver.st_midtier:szl_InstanceInformation is the instance password for the current Oracle Application Server 10g. The ias_admin user is the administrative user for Oracle Application Server instances and is required for software update installation on middle-tiers.

    While specifying the password, you must use the braces and specify the password in double quotation marks. For example, if you want to specify the password welcome1, then the syntax would be:

    oracle.iappserver.st_midtier:szl_InstanceInformation={"welcome1"}

    This password is same as the SYSMAN password that you specified when you first installed the Grid control in your environment.

    Note:

    After installing the Grid control in your environment if you change the SYSMAN password then ias_admin password will not get changed.

    To change the ias_admin password, go to the Oracle home directory of OMS and run the below command:

    $ORACLE_HOME/bin/emctl set password <Old ias_admin password> <New ias_admin Password>

    Note:

    If you do not remember the old ias_admin password then follow the instructions from Document ID 280587.1 on My Oracle Support (formerly Metalink) at http://metalink.oracle.com/

11. Apply the 10.2.0.5 patch set to the Oracle home directory of the OMS (for example, /abc/product/oms10g) by running the following command:

    ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp

12. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the OMS, run root.sh.

13. Apply the 10.2.0.5 patch set to the Oracle home directory of the Management Agent

    • Copy the patchset.rsp file from the <Patch Set DVD>/response/directory to a location on yourhost

    • Edit patchset.rsp to include the following:

      ORACLE_HOME = < Oracle home directory of the Management agent >
      

    • Apply the 10.2.0.5 patch set to the Oracle home directory of the Agent

      ./runInstaller -noconfig -silent -responseFile <absolute_path>/patchset.rsp

14. (ONLY FOR 10.2.0.5.0 OR HIGHER RELEASE) From the Oracle home directory of the Management Agent, run root.sh.

15. Set the PERL5LIB as <ORACLE_HOME>/perl/lib/5.6.1. where <ORACLE_HOME> is the Oracle home directory of the OMS.

16. Execute the following script to from the Oracle home directory of the OMS to complete the 10.2.0.5.0 install:

    $ORACLE_HOME/perl/bin/perl <ORACLE HOME>/sysman/install/ConfigureGC.pl <INSTALL_BASE_DIRECTORY>

    For example, if the Oracle home directory of OMS is /usr/oracle/gc/oms10g, then <INSTALL_BASE_DIRECTORY> must be /usr/oracle/gc.

17. After the script runs successfully, Grid Control is configured to 10.2.0.4 or higher release. To verify the release, do the following:

    • Go to the Oracle home directory of the OMS (for example, oms10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status oms

    • Go to the Oracle home directory of the Management Agent (for example, agent10g) and run the following command:

      $<ORACLE_HOME>/bin/emctl status agent

      Note:

      For 10.2.0.5, unsecured access to Grid Control (using HTTP URL) is restricted by default. Instead, use HTTPS URL. If you still want to use the HTTP URL, then unlock it using the following command from the Oracle home directory of the OMS:

      emctl secure unlock -console