Last updated: February 2009

This document contains the following sections:

1. Introduction

2. Installing Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.1/10.2.0.2) and upgrading it to Oracle Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)

3. Upgrading any existing Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.x)to Oracle Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)

4. Upgrading any existing Oracle Management Agent Release 1 (10.1.0.x) or Release 2 (10.2.0.x) or higher to Oracle Management Agent Release 5 (10.2.0.5)

----------------------
1. Introduction
----------------------

This document provides information about installing and upgrading Oracle Enterprise Manager 10g Grid Control and Oracle Management Agent for the following cases:

-----------------------------------------------------------------------------------------------------------------------------
# | Pre-Upgrade Release | Post-Upgrade Release
-----------------------------------------------------------------------------------------------------------------------------
1 | Enterprise Manager 10g Grid Control Release 2 (10.2.0.x) | 10.2.0.5
2 | Management Agent 10.1.0.x and(or) 10.2.0.x or higher | 10.2.0.5

-----------------------------------------------------------------------------------------------------------
1.1 Download Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)
-----------------------------------------------------------------------------------------------------------

Download the GridControl_10.2.0.5_<platform name>.zip patch set installation archive from the following location to any directory of a host where Oracle Management Service (OMS) is running.

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

----------------------------------------------------------------------------------------------------------
1.2 Enter the following command to extract the installation files:
----------------------------------------------------------------------------------------------------------

$ unzip GridControl_10.2.0.5_<platform name>.zip

This command extracts the following files and directory:
|- p3731593_10205_<platform name>.zip
|- 3731596.zip
|- 3822442.zip
|- README.txt
|- doc/

NOTE: <platform name> will be "LINUX" or "Win32" depending on the platform for which you are installing. For installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5), refer to the Release Notes available in the "doc" directory.

- p3731593_10205_<platform name>.zip is the ZIP file that contains 10.2.0.5 patch set software.

This zip can be used for:
- Upgrading Oracle Management Service Release 2 (10.2.0.x) or higher to Oracle Management Service Release 5 (10.2.0.5)
- Upgrading Oracle Management Repository (sysman schema)
- Upgrading Oracle Management Agent on the host where OMS is running.

NOTE: This will not upgrade the database in which the Management Repository (sysman schema) resides.

- 3731596.zip is for patching Management Agent by staging the patch set. To understand how you can apply the Management Agent 10.2.0.5 patch set, refer to method 2 described in section 4.3.3 "Upgrading Management Agent - Multiple Hosts at a Time" of the Release Notes. The Release Notes can be found in the "doc" directory.

- 3822442.zip is for patching Management Agent by distributing the full patch set. To understand how to apply the Management Agent 10.2.0.5 patch set, refer to method 1 described in section 4.3.3 "Upgrading Management Agent - Multiple Hosts at a Time" of the Release Notes. The Release Notes can be found in the "doc" directory.

-----------------------------------------------------------------------------------------------------------------------------
2. Installing Enterprise Manager 10g Grid Control Release 2 (10.2.0.1/10.2.0.2) and upgrading it to Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)
-----------------------------------------------------------------------------------------------------------------------------

In order to install Enterprise Manager 10g Grid Control Release 5 (10.2.0.5), you must have 10.2.0.1.0 (10.2.0.2.0 for Windows) release up and running.

The Enterprise Manager Grid Control software can be downloaded from the following location:
http://www.oracle.com/technology/software/products/oem/index.html

---------------------------------------------------------------------------------------------------------
2.1 Installing Enterprise Manager 10g Grid Control Release 2 (10.2.0.1)
---------------------------------------------------------------------------------------------------------

Installing Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) requires previous release of Grid Control to be 10.2.0.1.0.or higher (10.2.0.2.0 or higher for Microsoft Windows) . If you do not have a previous release, but want to have a 10.2.0.5.0 Grid Control environment, then first install 10.2.0.1.0 Grid Control and then upgrade it to 10.2.0.5.0.

A. Download Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) from the following location:

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

Refer to the Enterprise Manager Grid Control Installation and Basic Configuration Install guide for the instructions on installing the Grid Control 10.2.0.1.0 available at the following URL. This URL takes you to the Enterprise Manager documentation library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.

http://www.oracle.com/technology/documentation/oem.html

B. Installing Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) or higher:

If you do not have Grid control installed in your environment, then fast and recommended method is to perform a software-only installation of 10.2.0.5.

Refer to "Installing Software-Only and Configuring Later" described in Enterprise Manager Grid Control Installation and Basic Configuration Guide available at the following URL. This URL takes you to the Enterprise Manager documentation library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.

http://www.oracle.com/technology/documentation/oem.html

This method does not require any DST patches because we will be upgrading the Grid Control 10.2.0.1.0 to 10.2.0.5.0 directly using the software-only installation method .

You can also perform the Grid Control installation using Oracle Universal Installer as described in the Enterprise Manager Grid Control Installation and Basic Configuration Guid available at the following URL. This URL takes you to the Enterprise Manager documentation library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.

http://www.oracle.com/technology/documentation/oem.html

Download the GridControl_10.2.0.5_<platform name>.zip patch set installation archive to any directory on the host where Oracle Management Service is running. The patch set can be downloaded from the following location:
http://www.oracle.com/technology/software/products/oem/index.html

To understand how to patch Oracle Management Service Release 2 (10.2.0.1) to 10.2.0.5.0, refer to section 4.2 "Upgrading Oracle Management Service" of the Release Notes.

------------------------------------------------------------------------------------------------
2.2 Preinstallation steps before upgrading to Oracle Enterprise Manager Grid Control 10.2.0.5.0
------------------------------------------------------------------------------------------------

1. Oracle recommends that you back up the Oracle home that will be upgraded using this Patch Set. In the case of a Management Repository, Oracle recommends that you 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 10.2.0.5.0 patchset.
For information about platform-specific package and kernel requirements, refer to the Enterprise Manager Grid Control Installation and Basic Configuration Guide available at the following URL:

http://www.oracle.com/technology/documentation/oem.html

Above URL takes you to the Enterprise Manager documentation library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.

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 512 MB. For information about the fixed initialization parameter values, refer to the preinstallation requirements described in the Enterprise Manager Grid Control Installation and Basic Configuration Guide available at::
http://www.oracle.com/technology/documentation/oem.htm

Above URL takes you to the Enterprise Manager documentation library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.

4. Make sure that the Partitioning option is enabled in the Database housing the Grid control repository (Sysman schema)

Connected to the Database as sysdba and run the following query to see if the Partioning Option is installed:
SQL> select value from v$option where parameter = ‘Partitioning’;

Should give VALUE=TRUE.

Note: No additional partitioning license is required for the Database housing the Grid control repository, as it is basic Grid Control requirement.

5.Both the DBSNMP and SYSMAN users require the EXECUTE privilege on the DBMS_RANDOM package in the Repository Database. You must grant the privilege to both users as follows:

a. Log into the Repository Database as SYSDBA.
b. Run the following SQL:

SQL> grant execute on dbms_random to dbsnmp;
SQL> grant execute on dbms_random to sysman;

c. Verify that the query below does not return any invalid objects:
SQL> select object_name, object_type, owner from dba_objects where status='INVALID';

6. If the repository database is configured with the UTF8 character set, the value of the NLS_LENGTH_SEMANTICS needs to be set to BYTE.

To check this in the database:

SQL> SELECT value FROM nls_database_parameters
WHERE parameter='NLS_LENGTH_SEMANTICS';

If the value is not set to 'BYTE', change it by running this command:
SQL> ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=BYTE SCOPE=both;

7.If the database housing the Grid control repository is linked with a Data Guard database, before the upgrade starts, the database has to be forced in logging mode, 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;

8. If your Enterprise Manager is shutdown 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:
c) SQL> exec emd_maintenance.analyze_emd_schema('SYSMAN')
d) Start the Oracle management service

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

* Note *: Oracle recommends that you back up your 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 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, please 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 = "foo"
alter package foo compile;
if the object_type = "PACKAGE BODY" and object_name =
"foo" alter package foo compile body;

e) 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 steps.

10 a) Login as sysman in the Grid control Repository database

b) Run the below sql:

SET SERVEROUTPUT ON SIZE 4000
SET LINE 255

SPOOL run_after_upgrade.sql
begin
for rec in ( select TARGET_TYPE ,PROPERTY_VALUE FROM MGMT_TYPE_PROPERTIES WHERE TARGET_TYPE IN ( 'RHreposURL','SusereposURL','SolarisreposURL','WindowsreposURL','PatchCrossRef' ))
loop
begin
dbms_output.put_line('INSERT INTO MGMT_PATCHING_PROPERTIES(PROPERTY_TYPE,PROPERTY_NAME,PROPERTY_VALUE)values(''os_patching_repos_url'','''||rec.TARGET_TYPE||''','''||rec.PROPERTY_VALUE||''');');
end;
end loop;
dbms_output.put_line('COMMIT;');
end;
/
SPOOL OFF

DELETE MGMT_TYPE_PROPERTIES WHERE TARGET_TYPE IN ('RHreposURL','SusereposURL','SolarisreposURL','WindowsreposURL','PatchCrossRef' );

COMMIT;
/

c) The above step will generate a file 'run_after_upgrade.sql'. For example:

INSERT INTO MGMT_PATCHING_PROPERTIES(PROPERTY_TYPE,PROPERTY_NAME,PROPERTY_VALUE)values('os_patching_repos_url','RHreposURL','ftp://stack34.us.oracle.com/pub/rpm');
INSERT INTO MGMT_PATCHING_PROPERTIES(PROPERTY_TYPE,PROPERTY_NAME,PROPERTY_VALUE)values('os_patching_repos_url','RHreposURL','http://stang05.us.oracle.com/pub/');

COMMIT;

PL/SQL procedure successfully completed.

d) Open the file 'run_after_upgrade.sql' and check for any INSTERT statement.

+ If there are no INSTERT statement then you are not required to run this file after the Grid control upgrade is done successfully

+ If there are INSTERT statements then remove or comments out the line "PL/SQL procedure successfully completed" and then run the 'run_after_upgrade.sql'on the Grid control Repository database as sysman user after the Grid control upgrade is done successfully

11.If your 10.1.0.5.0 database housing the Grid control repository does not have CPU Jan 2008 patch 6826532 applied then make sure that you apply this patch or if you have applied latest CPU Jan 2009 patch 7592360 on your database housing the Grid control repository then you need not apply the old CPU Jan 2008 patch 6826532.

Note: CPU Jan 2008 patch 6826532 and CPU Jan 2009 patch 7592360 are not applicable on Windows platform

12. If you have applied the latest CPU Jan 2009 patch 7608318 to your Oracle Management Service (OMS) before upgrading, then you may receive a warning about patch conflict during the product specific prerequisite check. You can ignore this warning and continue with the 10.2.0.5.0 upgrade. The installer will automatically rollback the patch.

13.If you have applied the latest CPU Jan 2009 patch 7608318 to your Oracle Management Service (OMS) before upgrading, then make sure that permission of the following files under the Oracle home of directory of OMS <ORACLE_HOME>/rdbms/admin is set to 664.
(dbmsaqds.plb,dbmsaw.plb,prvtlmd.plb,prvtpexp.plb,prvtlsby.plb,prvtlms.plb,prvtaqip.plb,prvtstas.plb,prvtsqlt.plb,prvttxfm.plb,prvtaqdi.plb,prvtaqds.plb,prvtcdpu.plb,prvtcdpi.plb,prvtmeti.plb,prvtxdbz.plb,exfeapvs.plb,prvtdupg.plb,prvtupgi.plb,prvtkupc.plb,prvtbpw.plb,prvtaqiu.plb,prvtaqim.plb,prvtbsqu.plb,prvtbut4.plb,prvtmetu.plb,prvtmeta.plb,prvtcdcp.plb,prvtcdcu.plb )

If the permission is not set to 664 for the above files then during the upgrade you will get permission denied error,
For Example: Error in writing to file '/u01/app/oracle/product/10.2.0/oms10g/rdbms/admin/dbmsaw.plb' Permission denied

14. Before proceeding with the upgrade, make sure that the dbms jobs are stopped. To do this, follow these steps:
a) Login into the database as SYSMAN
b) Run the following SQL command:
SQL> execute emd_maintenance.remove_em_dbms_jobs;
SQL>commit;

c) Stop the Repository Database
d) Start the Repository Database

15.Make sure DBMS JOBS and DBMS Scheduler (for version 10.1+ RDBMS) in the Enterprise Manager Grid Control Repository are turned off during the Enterprise Manager schema upgrade process. To perform this task, follow these steps:

a.Log into the repository as SYSMAN.
b.For each instance, perform the tasks below:

1. Write down the values of job_queue_processes for each of the instances after you run the following command:

SQL> select a.instance_name as sid, b.value as jobqueue from gv$instance a, gv$parameter b where a.inst_id = b.inst_id and b.name='job_queue_processes';

2. Turn off DBMS JOBS by running the following command:
SQL> alter system set job_queue_processes=0 sid='*';

Be sure there were no active jobs running by waiting until the following query returns 0:
SQL> select count(*) from dba_jobs_running;

3. Turn off the DBMS Scheduler by running (for version 10.1+ RDBMS) the following command:

SQL> exec dbms_scheduler.set_scheduler_attribute ('SCHEDULER_DISABLED','TRUE');

Be sure there were no active schedules running by waiting until the following query returns 0 (for version 10.1+ RDBMS):

SQL> select count(*) from dba_scheduler_running_jobs where SLAVE_PROCESS_ID IS NOT NULL;

After the upgrade is completed, turn on DBMS JOBS and DBMS Scheduler (for version 10.1+ RDBMS) for each instance by performing the following steps:

a.Log into the repository as SYSMAN
b.Turn on DBMS JOBS by setting the job_queue_processes to the values written down earlier for each instance
c.Turn on DBMS Scheduler (10.1+ RDBMS) using the following command:
SQL> exec dbms_scheduler.set_scheduler_attribute ('SCHEDULER_DISABLED','FALSE');

16. The script preinstall.pl, which can be found at the top directory of the extracted patch set, must be run as perl preinstall.pl <OMSHome> before a Grid Control 10.2.0.5 OMS upgrade if the one-off #7214697 was applied in the OMSHome before the upgrade. However if the one-off was not applied, running the script will not cause an issue.

Note: Refer to upgrade checklist Note 464674.1 the on My Oracle Support. This note will be updated frequently with the latest information.

--------------------------------------------------------------------------------------------------------------------------
3 Upgrading any existing Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.x) or higher to Oracle Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)
--------------------------------------------------------------------------------------------------------------------------

Make sure that you follow the Preinstallation steps decribed in the above section 2.2 before upgarding any existing Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.x) or higher to Oracle Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)

Note: Make sure that you first upgrade the Oracle Management Service (OMS), and then the Management Agent before upgrading the
database that contains the Management repository (sysman schema)

Enter the following command to unzip and extract the installation files from the downloaded software. For details on how to download the software refer to section 1.2 above.

$ unzip p3731593_10205_<platform name>.zip
This extracts the files to the "3731593" directory.

+ Navigate to the 3731593/Disk1 subdirectory

$ cd 3731593/Disk1

+ Set the ORACLE_HOME variable to the Oracle home directory of Oracle Management Service (OMS).

+ Execute the runInstaller
$ ./runInstaller

Note: This will only upgrade your OMS and Management repository (sysman schema)

+ Set the ORACLE_HOME variable to the Oracle home directory of Management Agent.

+ Execute the runInstaller
$ ./runInstaller

Note: This will only upgrade your Management Agent residing on the OMS host.

For detailed instructions refer to section 4 "Installation Procedure" of the Release notes under the "doc" directory.

The upgrade process then upgrades the Oracle Management Service (OMS), Oracle Management Repository and the Management Agent on the same host as the OMS to the latest Enterprise Manager 10g Release 5 (10.2.0.5). This will not upgrade the Database in which Management repository resides.

-----------------------------------------------------------------------------------------------------------------------------
4. Upgrading any existing Oracle Management Agent Release 1 (10.1.0.x) or Release 2 (10.2.0.x) or higher to Oracle Management Agent Release 5 (10.2.0.5)
--------------------------------------------------------------------------------------------------------------------------

4.1 Upgrading Oracle Management Agent Release 1 (10.1.0.x) to Oracle Management Agent Release 5 (10.2.0.5)
-----------------------------------------------------------------------------------------------------------

If your Additional management agent version is 10.1.0.x and you want to upgrade it to 10.2.0.5 version then you have to first download the 10.2.0.5.0 Agent Software from the Oracle Technology Network (OTN):-

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

Follow the instructions to upgrade the management agent from the Chapter "Upgrading Enterprise Manager Grid Control" of the Enterprise Manager Grid Control Installation and Basic Configuration Guide available at-

http://www.oracle.com/technology/documentation/oem.html

This URL takes you to the Enterprise Manager documentation library page, and this URL may appear in many parts of the Release Notes. Access this URL to reach the library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.

4.2 Upgrading Oracle Management Agent Release 1 (10.2.0.x) to Oracle Management Agent Release 5 (10.2.0.5)
-----------------------------------------------------------------------------------------------------------

If you have Additional management agent version 10.2.0.x or higher and want to upgrade it to 10.2.0.5 version then follow the steps from the section "Upgrading Management Agent" of the Release note.