OEM GRID CONTROL UPGRADE FROM 10.2.0.1 to 10.2.0.5 (Part 1)

1. Pre-installation Tasks

    The following are the general pre-installation tasks.

1. Back up the Oracle home that will be upgraded using this patch set. In the case of a Management Repository, Oracle recommends to back up the repository database before applying the patch set because the patch set makes changes to the repository that cannot be rolled back. Also, back up the Oracle Inventory directory.

2. Make sure that you meet the product pre-requisites (operating system patches, packages etc.) for the 10.2.0.5 patch set.

3. Before upgrading your Oracle Management Service, ensure that the shared pool size is set in your Grid Control repository database as per your infrastructure. Minimum size for shared pool is 512 MB.

4. If the database housing the Grid Control repository is linked with a Data Guard database, the database must be forced in logging mode before the upgrade starts to force all index maintenance commands to be propagated to the standby database.

The upgrade by default will perform the index maintenance commands in a 'NOLOGGING' mode. This means that any Data Guard database linked to the repository database will not have these index operations replicated to it.

To make sure these commands get replicated to the Data Guard instance, force the database into logging mode:

SQL> CONNECT / AS SYSDBA;
SQL> ALTER DATABASE FORCE LOGGING;

Once the OMS upgrade is successful then revert the Data Guard force logging changes:

SQL> CONNECT / AS SYSDBA;
SQL> ALTER DATABASE NO FORCE LOGGING;

5. If your Enterprise Manager is shut down for a long period of time, you must follow the below steps before conducting the upgrade:

a. Log into the Repository Database as SYSMAN

b. Run the following SQL:
   
   SQL> exec emd_maintenance.analyze_emd_schema('SYSMAN');

c. Start the Oracle management service
   Go to /OracleHomes/oms10g/BIN
   $./emctl start oms

6. Make sure that there are no invalid sysman objects present in Grid Control repository.

Important: Oracle recommends to back up database before you perform the upgrade operation. Perform the following steps before upgrading:

a. Login into the Database as SYS user.

b.Check if there are any invalid SYSMAN objects.

SQL> select object_name, object_type from all_objects where owner='SYSMAN' and status <> 'VALID';

The above query should return 0 rows. If there are rows, then run the below SQL statement:SQL> @admin_recompile_invalid.sql SYSMAN

The admin_recompile_invalid.sql script is available under
<ORACLE_HOME>/sysman/admin/emdrep/sql/core/latest/admin/

Where <ORACLE_HOME> is the Oracle home directory of the Oracle Management Service (OMS).

c. Go to step b again to be sure all SYSMAN objects are valid. If you still have invalid SYSMAN objects that are not in the Recycle bin, contact Oracle support.

d. Check to be sure there is no invalid SYS object:

SQL> select object_name, object_type from all_objects where status<>'VALID' and object_name like 'DBMS%'; 
 The above query should return 0 rows. If there are rows, then try to "recompile" them.
 For example:

if the object_type = "PACKAGE" and object_name = "ABC"
alter package abc compile;
if the object_type = "PACKAGE BODY" and object_name =
"ABC"
alter package abc compile body;

7. If any of the packages fail to become valid even after recompilation, then Contact Oracle Support to assist you. Once this verification is done, continue through with the rest of the pre-installation tasks.

                                                             -------------------> To be continued in Part II