This document contains the following section

1. Introduction

2. Fresh Installation of Enterprise Manger 10g Grid Control Release 2 and upgrading it to Release 4

3. Upgrading the 10.1.0.x (or) 10.2.0.x or higher Management Agent version to 10.2.0.4

1. Introduction
-------------------
This document provides information about installing and upgrading Enterprise Manager 10g Grid Control Release for following cases:

No | Pre-Upgrade Release | Post-Upgrade Release
---------------------------------------------------------------------------------------
1 | Grid Control 10.2.0.x Install | 10.2.0.4
2 | Management Agent 10.1.0.x and(or) 10.2.0.x or higher | 10.2.0.4

1.1 Download Enterprise Manger 10g Grid Control 10.2.0.4
---------------------------------------------------------

Download the GridControl_10.2.0.4_<platform name>.zip patch set installation archive to any directory on the host, which has the Oracle Management Service running on. The patch set can be downloaded from the following location:

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

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

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

This will extract following files and directory:
|- p3731593_10204_<platform name>.zip
|- 3731596.zip
|- 3822442.zip
|- p4329444_10104_< platform name >.zip (will not be present for Windows)
|- p4329444_10105_< platform name >.zip (will not be present for Windows)
|- README.txt
|- doc/

Refer to Release Note under the "doc" directory for installing 10.2.0.4.0

- p3731593_10204_<platform name>.zip is the zip that contains 10.2.0.4.0 patch set software. This zip can be used for upgrading Oracle Management Service (OMS) versions 10.2.0.1 or higher, the repository (Note that this will not upgrade the database) and the agent on the host where the OMS is running.

- 3731596.zip is for patching agent by staging the patch set. Please look at the Release Notes section 4.3.3 method 2 under the "doc" directory on how to apply the agent 10.2.0.4.0 patch set

- 3822442.zip is for patching agent by distributing the full patch set. Please look at the Release Notes section 4.3.3 method 1 under the "doc" directory on how to apply the agent 10.2.0.4.0 patch set

- p4329444_10104_< platform name >.zip is zip that contains patch for bug 4329444 for "<platform name>" for RDBMS version 10.1.0.4.0

- p4329444_10105_< platform name >.zip is zip that contains patch for bug 4329444 for "<platform name>" for RDBMS version 10.1.0.5.0

2. Fresh Installation of Enterprise Manger 10g Grid Control Release 2 and upgrading it to Release 4
-------------------------------------------------------------------------------------------------------------------------------------

In order to install Enterprise Manager 10g Grid Control Release 4, you must have 10.2.0.1.0 Grid Control or higher up and running.

The 10.2.0.1 Grid control software can be downloaded from -
http://www.oracle.com/technology/software/products/oem/index.html

2.1 Install Oracle Enterprise Manager Grid Control 10.2.0.1
------------------------------------------------------------

Installing 10g Grid Control Release 4 requires previous release of Grid Control to be 10.2.0.1.0.or higher. If you do not have a previous release, but want to have a 10.2.0.4.0 Grid Control environment, then first install 10.2.0.1.0 Grid Control and then upgrade it to 10.2.0.4.0.

A. Download Oracle Enterprise Manager Grid Control 10.2.0.1 from:

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

To install 10.2.0.1.0 Grid control refer to the Install guide for the instructions, avaliable at :-
http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10953/toc.htm

B. Installing Oracle Enterprise Manager Grid Control 10.2.0.4:

Download the GridControl_10.2.0.4_<platform name>.zip patch set installation archive to any directory on the host, which has the Oracle Management Service running on. The patch set can be downloaded from the following location:

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

Please refer the Release Note section 3.2.1 to patch the 10.2.0.1 Oracle management service to 10.2.0.4.0.

Note :
*******************************************************************************************************************************************
The fast and recommended method is to perform a software only installation of 10.2.0.1.0 and then upgrade it to 10.2.0.4.0.
Refer to section - Installing Software-Only and Configuring Later, available at :
http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10953/installing_em.htm#CCHGBDCB

This method doesn't require any DST patchses,since we will be upgrading the Grid control 10.2.0.1.0 to 10.2.0.4.0 directly using the 'Software-Only' and Configuring Later method.
*******************************************************************************************************************************************

2.2 Apply required patches to Oracle Enterprise Manager grid control 10.2.0.1.0 or higher before upgrading to 10.2.0.4.0 grid control
-----------------------------------------------------------------------------------------------------------------------------------

In the case of Grid Control environment installed via "Enterprise Manager using New Database" option ,repository database version will be 10.1.0.4.0. Before upgrading Grid control 10.2.0.1.0 or higher to 10.2.0.4.0 you must apply the 4329444 patch on the repository database.

If you have alreay applied 4329444 patch on the 10.1.0.4.0 repository database then you are not require to apply the patch again.

In the case of Grid Control environment installed via "Enterprise Manager using Existing Database" option by using 10.1.0.4.0/10.1.0.5.0 database as a repository database of the Grid control then before upgrading the Grid control 10.2.0.1.0 or higher to 10.2.0.4.0 please apply the 4329444 patch on the repository database.

If you have alreay applied 4329444 patch on the 10.1.0.4.0/10.1.0.5.0 repository database then you are not require to apply the patch again.

Instructions for Applying Patch 4329444
------------------------------------------

Apply the patch for bug 4329444 on the Repository Database Home. In order to apply this patch for the AIX 5L platform:

+ Unzip the file p4329444_10104_<platform name>.zip from the downloaded image described in section 1.2 using following command:

$ unzip p4329444_10104_<platform name>.zip

+ Follow the instruction in 4329444/README.txt to apply the patch to repository database

* Important *: Oracle recommends that you take back up of your database before you perform the upgrade operation. Note that the patch 4329444 might conflict with some previous CPU releases (for example April 2007 CPU) that might be applied to your repository database. In case of a conflict while applying patch 4329444 DO NOT continue with the upgrade process. Contact Oracle support to first resolve the patch conflict and then perform the following steps before performing the upgrade

1. Login into the Database as SYS user

2. 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 OMS.

3. Go to step 2 again to be sure all SYSMAN objects are valid.If you still have invalid SYSMAN objects that are not in recycle bin, please contact Oracle support.

4. Check there is no invalid SYS object
SQL> select object_name, object_type from all_objects where status<>'VALID' and object_name like 'DBMS%';

5. 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;

6. If any of the packages fail to become valid even after recompilation, then Contact Oracle Support to assist you.
Once this verification is done, execute the following command to resume the upgrade process

a. Go to <ORACLE_HOME>/oui/bin, where ORACLE_HOME is the Oracle home directory of the OMS and then execute the following command-

./runConfig.sh ORACLE_HOME=<OMS_ORACLE_HOME> ACTION=patchsetConfigure MODE=perform COMPONENT_XML={oracle.sysman.top.oms.10_2_0_4_0.xml}

2.3 Check for the Patches before Upgrade
-----------------------------------------

+If you have applied the patch 5478872 to your Enterprise Manager Grid Control environment, then you MUST drop the index MGMT_DELTA_SNAP_IDX3 before upgrading Grid Control to 10.2.0.4. If the index is not dropped, the upgrade process will fail.
To drop the index MGMT_DELTA_SNAP_IDX3, run the following command:

a. Connect to SQL Plus session as EM repository owner (SYSMAN)
b. Issue the command SQL> drop index MGMT_DELTA_SNAP_IDX3

*Note*-The fix for bug 5478872 is included in the patch set version 10.2.0.4 so you are not required to apply any additional patches to resolve this bug
after upgrading to the 10.2.0.4 version of Grid Control.

You can also refer to the Metalink Note 558673.1.

+ If you have applied the patch 6606233 to your Enterprise Manager Grid Control environment, then you MUST roll back the patch before upgrading
Grid Control to 10.2.0.4.After rolling back the patch, upgrade Grid Control to 10.2.0.4 and then apply patch 6606233 that is specific to 10.2.0.4 Grid Control.

Refer to the Patch Read me for Patch Rollback Instructions.

Refer to Metalink Id 464674.1 for more information on Upgrading to Grid control release 4

2.4 Executing required SQLs against repository
-------------------------------------------------
If you are using the corrective actions feature in your existing 10.2.0.3.0 deployment, then you may run into a schema inconsistency, which can cause an upgrade to fail (bug 5855008). If you are using corrective actions, then execute the following PL/SQL block in the Enterprise Manager repository using sqlplus (connected as SYSMAN), BEFORE doing the upgrade, in order to clean up the inconsistent data.

BEGIN
FOR r IN (SELECT job_id
FROM mgmt_corrective_action a
WHERE NOT EXISTS
(SELECT 1
FROM mgmt_job j
WHERE j.job_id = a.job_id)
) LOOP
UPDATE mgmt_policy_assoc_cfg c
SET crit_action_job_id = NULL
WHERE crit_action_job_id = r.job_id
;
UPDATE mgmt_policy_assoc_cfg c
SET warn_action_job_id = NULL
WHERE warn_action_job_id = r.job_id
;
UPDATE mgmt_policy_assoc_cfg c
SET info_action_job_id = NULL
WHERE info_action_job_id = r.job_id
;
DELETE
FROM mgmt_corrective_action
WHERE job_id = r.job_id
;
COMMIT;
END LOOP;
COMMIT;
END;
/

* Note *: If your repository is housed in a 10.1.0.4 or 10.1.0.5 database running on windows platform then you are *NOT* required to apply this patch to the database. Skip to section 2.5 of this README.

2.5 Upgrade to Oracle Enterprise Manager 10g Release 4
----------------------------------------------------

Follow the below steps to upgrade the Enterprise Manager 10g Release 4

+ Enter the following command to unzip and extract the installation files from the downloaded image described in section 1.2:

$ unzip p3731593_10204_<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

For detailed instructions refer to section 3.2 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 4 version.

*Important *: The same Patch Set can be used for patching OMS, Repository, and Management Agent. For more detail on installing the patch set, refer to the release note.

Refer to Metalink Id 464674.1 for more information on Upgrading to Grid control release 4

2.6 Optional: Upgrading Repository Database to 10.2.0.3 or higher 10.2.0.X patch set
-------------------------------------------------------------------------------------

If you installed Grid Control 10.2.0.3.0 via "Enterprise Manager using New Database" option, your repository database version will be 10.1.0.4. In order to upgrade your repository database to 10.2.0.3 or higher 10.2.0.X version, follow the steps below after upgrading your Grid Control environment to Enterprise Manager Grid Control 10.2.0.4

+ Upgrade the Grid Control to 10.2.0.4.0

+ Upgrade the repository database to 10.2.0.3 by following the steps from the Metalink Note 399520.1

3. Upgrading the 10.1.0.x (or) 10.2.0.x or higher Management Agent version to 10.2.0.4
----------------------------------------------------------------------------------------
Refer to Metalink Id 464674.1 for more information on Upgrading to Grid control release 4

3.1 Upgrading the 10.1.0.x Management Agent to 10.2.0.4
--------------------------------------------------------
If your Additional management agent version is 10.1.0.x and you want to upgrade it to 10.2.0.4 version then you have to download the Agent Software Kit from the OTN :-

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

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

http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10953/toc.htm

3.2 Upgrading the 10.2.0.x or higher Management Agent to 10.2.0.4
------------------------------------------------------------------

If you have Additional managemnet agent version 10.2.0.x or higher and want to upgrade it to 10.2.0.4 version then follow the steps from the section 4.3 of the Release note.