In this Document
  Goal
  Solution
  References

Applies to:

Goal

Solution

Database Prerequisites:

All of the requirements of the Grid Control installation with a new database must be met as described in the Oracle? Enterprise Manager Grid Control Installation Guide, 10g Release 5 (10.2.0.5.0). This document describes general (i.e, must be an enterprise edition with fine grained access control active) and specific (i.e., initialization parameters) requirements for the existing database. Note that a default enterprise edition database installation is not sufficient for use as a Grid Control repository due to these general and specific requirements, but must be configured to meet them.

Additionally, the database must be free of any prior repository contents, whether for Database Control or Grid Control. Use emca, RepManager or the manual procedure in Note.278100.1 to remove an existing repository before installing Grid Control with the existing database. Use of the emca utility is described in chapter 1 of Oracle? Enterprise Manager Advanced Configuration, 10g Release 5 (10.2.0.5). Use of RepManager is described in chapter 9 of the same document, available on the OTN Enterprise Manager documentation site.

Lastly, the database must be a version currently certified for database support and use as a Grid Control repository as shown in the Certify section of My Oracle Support.



Software Only Procedure:

To install Enterprise Manager Grid Control 10.2.0.5.0 using an existing 11g database with the silent, software-only method, follow these steps:


A. Install Source Staging and Response File Preparation

1. Place the base product install stage for Linux (10.2.0.1.0) in an accessible directory: i.e., /u02/gc10201

2. Modify the base install response file for the "Grid Control with an existing database" install type, located at: /u02/gc10201/response/em_using existing_db.rsp.

Generic filepath form:

/response/em_using_existing_db.rsp

3. Alter the following parameters from default as follows (archive this file before alterations):

4. Place the 10.2.0.5.0 Grid Control patchset in a different staging location, i.e., /u02/gc10205

5. Make a copy of the patchset response file located at:

/u02/gc10205/3731593/Disk1/response/patchset.rsp

generic filepath form:

//3731593/Disk1/response/patchset.rsp

6. Rename the copy in place to oms_patchset.rsp.

Alter the following parameters from default as follows in the oms_patchset.rsp file:

7. Make a copy of the patchset response file located at:

/u02/gc10205/3731593/Disk1/response/patchset.rsp

generic filepath form:

//3731593/Disk1/response/patchset.rsp 

8. Rename the copy in place to agent_patchset.rsp.

9. Alter the following parameters from default as follows in the agent_patchset.rsp file:

10. Verify the 11.1.0.6.0 database characteristics are as specified in this reference, available on OTN:

Oracle? Enterprise Manager Grid Control Installation Guide
10g Release 5 (10.2.0.5.0)

Chapter 3 and Chapter 7 show what is required of an existing database for repository use. A default installation of an Enterprise Edition database is not sufficient to support a repository.


B. Product and Patchset Installation without Configuration

1. Install the base release (10.2.0.1.0) for Linux using the following command:

generic command form:

Notes:

- Install in an existing, empty directory.

- Base product installation will be logged in two installActions<>.log files located in:

- In addition, the installActions<>.log for each component is located in:

These two installActions<>.log files will represent the installations of the oms10g and agent10g Oracle Homes in time sequence. Note that the configuration assistant content normally to be found in the agent installActions<>.log (last in the time sequence) will be missing due to the “-noconfig” option used in the runInstaller command.

2. Log in as a root user in a new command session and run the following scripts on the host where the base release of Enterprise Manager Grid Control is installed, when prompted by the installer:

If this is the first Oracle product you just installed on the host (i.e., no /etc/oraInst.loc file exists yet), then run the orainstRoot.sh script from the Central Inventory:

Run the allroot.sh script from the Oracle home directory of the OMS:

3. Certain opmn processes will be running merely as a result of installation, in spite of the fact that no configuration of the OMS Oracle Home has been performed. Stop these OPMN processes by running the following command from the Oracle Home directory of the OMS:

4. Apply the 10.2.0.5.0 patchset to OMS Oracle Home:

Note that the 10.2.0.1.0 Grid Control base product installation is loaded with the proper system prerequisite checks and the patchset also has the ability to check for EL4 prerequisites, so the "-ignoreSysPrereqs" option should not be used for any of the installations in this procedure.

 generic command form:

 Logging for the oms patchset application will be in the installActions<>.log for the patchset application found in either of these locations:

The installActions<>.log for the OMS patchset application will be later in timestamp than the three files created during installation. Again, no configuration assistant logging will be included due to the -noconfig option used in the runInstaller command.

5. Run the root.sh command:

No feedback will be given on successful execution in this case.

6. Apply 10.2.0.5.0 patchset he agent Oracle Home:

generic form:

Logging for the agent patchset application will be in the installActions<>.log for the patchset application found in either of these locations:

The installActions<>.log for the agent patchsest application will be later in timestamp than the three files created during installation or the file created during oms patchset application. Again, no configuration assistant logging will be included in the associated installActions<>.log due to the -noconfig option used in the runInstaller command.

7. Run the root.sh command as root:

 
C. Configuring the Grid Control Installation with the ConfigureGC.pl Script

1. Ensure that the .../db10g/oui/bin/runConfig.sh file has ’execute’ permission.

2. Use the following procedure to preserve and set the PERL5IB environment variable:

Make a backup of the PERL5LIB variable value:

Set PERL5LIB:

3. Configure Enterprise Manager Grid Control by running the ConfigureGC.pl script:

generic form:

 
Logging for this action will start in the:

 
As the configuration assistants are run through the progress of the script, ORACLE_HOME/cfgtoollogs/cf**/ files will begin to populate with the results of these configuration actions for each Oracle Home in its respective directory (i.e., .../db10g/, .../oms10g/ or .../agent10g/). As operational actions (i.e., process start) are taken in the configuration steps, operational logs will be populated in these locations:

among others.

4. The configuration may take around an hour with little command session update at times.
It may be instructive to follow the progress of the configuration in these files, alternative to the command session:

Likely failure scenario (Note 602750.1, Bug 7483221):

a) The command session will eventually issue a failure message, indicating to look in the .../oms10g/cfgtoollogs/cf**/CfmLogger<>.log file.
The .../oms10g/cfgtoollogs/cf**/CfmLogger<>.log file and the emca_repos_drop<>.log will both show error code ORA-01017 logged. The emca_repos_drop<>.log shows this message, for example:

[20-02-2009 14:25:49] Could not connect to SYS/(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=
(PROTOCOL=TCP)(HOST=gamma.clspco.adelphia.net)(PORT=1523)))(CONNECT_DATA=(SID=db111))):
ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin

b) To work around this failure, log in to the repository database as SYS or SYSTEM and issue this update:

c) Run the ConfigureGC.pl script again, repeating the syntax used in the first execution (leaving any current operating processes intact):

d) The configuration will pick up where it left off, so repository creation will succeed, base OMS configuration will complete, agent comfiguration will complete and the patchset configuration actions will start. The configuration will again fail, with a command session message to review the new .../oms10g/cfgtoollogs/cf**/CfmLogger<>.log file, which will show the ORA-01017 error again.

To work around the second failure, log in to the repository database as SYS or SYSTEM and issue this update, using the password value originally configured in the em_using_existing_db.rsp response file (password value shown is only for example):

 f) Run the configuration script for a third time, repeating the syntax as before (leaving any current operating processes intact):

5. Successful finish of the configuration script will be denoted by this kind of messaging in the command session (ignore date):

6. Verify the 10.2.0.5.0 component version for the OMS in any of these ways:

 
7. Verify the OMS' new Application Server version (10.1.2.3.0) in any of these ways:

8. Verify the 10.2.0.5.0 component version for the agent in any of these ways:

9. Review the post patch requriements of Note 853691.1 "ALERT: Important Upgrade Steps Required for Enterprise Manager Grid Control 10gR5 (10.2.0.5) Upgrades" for OMS and agent patching requirements of the 10.2.0.5.0 version. This is also a good time to apply the pre-patch database maintenance actions from this note, if appropriate, if this was not done before 10.2.0.5.0 patchset application to the OMS.

D. Troubleshooting Failure if EM_DBMS_JOBS are running during configuration

1) The ConfigureGC.pl script will fail if EM_DBMS_JOBS are running, This can be determined from the .../db10g/cfgtoollogs/oui/configActions<>.log or the .../db10g/cfgtoollogs/cf**/CfmLogger<>.log.

In this case, refer to the Oracle? Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 4 (10.2.0.5), available at the Oracle Technology Network web site.


2) Database bug 5345437 may be encountered after patched agent startup. This bug prevents the agent from completing upload at some point, after initial upload success. The agent will continue to operate, but cannot upload further and cannot upload on restart. Applying the 5345437 database bugpatch to the repository database will allow the agent to continue to upload regularly.



Published Documentation References:

Oracle? Enterprise Manager Grid Control Installation Guide
10g Release 5 (10.2.0.5.0)

Oracle? Enterprise Manager Advanced Configuration
10g Release 5 (10.2.0.5)

Oracle? Enterprise Manager Grid Control Release Notes for Linux and Microsoft Windows
10g Release 4 (10.2.0.5.0)

References
Bug 5345437 - APPS BUG5286029:ORA-20001: HZ_API_OTHERS_EXCEP: N, ERROR, ORA-01801: DATE FORMAT
Bug 7483221 - CONFIGUREGC.PL IS FAILING WITH INVALID PASSWORD FOR SYS
Note 602750.1 - ConfigureGC.pl Reports - Invalid Username/Password.

References