Yesterday while installing OEM Grid Control 10gR2 (10.2.3) I got the following error:

As I’ve accustomed to get some errors (or hit a bug) either during Grid Control installation, or configuration, I was calm and after some time found the following documentation which describes the error:

How to Recover From Enterprise Manager Grid Control 10g Base Releases (10.2.0.x.0) Installation Errors after 31-Dec-2010 [ID 1228103.1]

And here’s the explanation

The Enterprise Manager Grid Control 10g base releases used a fixed end date for the root certificate used to setting up secure communications via the Secure Socket Layer (SSL) protocol. The fixed date used is the 31-Dec-2010 00:00:00 UTC.

The certificate expiration will cause errors to occur if you attempt to install these releases on or after 31-Dec-2010.

Amazing .. Anyway, the solution was adding a Patch and making some configuration changes. Here’re the steps what I’ve done:

Firstly, you need to download and install the Patch 8430622 from metalink

Patch 8430622: LX10201-RECUT(TC3): OMS CONFIG FAILED DUE TO HTTP_SERVER’S MAXIMUM RETRY LIMIT

After downloading the file, copy it to the server, extract it and patch

[code]

[oracle@Server orasoft]$ unzip p8430622_10203_GENERIC.zip

Archive:  p8430622_10203_GENERIC.zip

creating: 8430622/

creating: 8430622/files/

creating: 8430622/files/sysman/

creating: 8430622/files/sysman/jlib/

creating: 8430622/files/sysman/jlib/emagentSDK.jar/

creating: 8430622/files/sysman/jlib/emagentSDK.jar/oracle/

creating: 8430622/files/sysman/jlib/emagentSDK.jar/oracle/sysman/

creating: 8430622/files/sysman/jlib/emagentSDK.jar/oracle/sysman/eml/

creating: 8430622/files/sysman/jlib/emagentSDK.jar/oracle/sysman/eml/sec/

creating: 8430622/files/sysman/jlib/emagentSDK.jar/oracle/sysman/eml/sec/util/

inflating: 8430622/files/sysman/jlib/emagentSDK.jar/oracle/sysman/eml/sec/util/RootCert.class

inflating: 8430622/README.txt

creating: 8430622/etc/

creating: 8430622/etc/xml/

inflating: 8430622/etc/xml/ShiphomeDirectoryStructure.xml

inflating: 8430622/etc/xml/GenericActions.xml

creating: 8430622/etc/config/

inflating: 8430622/etc/config/inventory

inflating: 8430622/etc/config/actions

[oracle@Server orasoft]$

[/code]

Switch to $OMS_HOME/bin folder and stop the OMS

[code]

[oracle@Server bin]$ ./emctl stop oms

Oracle Enterprise Manager 10g Release 3 Grid Control

Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.

Oracle Management Server is Down.

[oracle@Server bin]$

[/code]

Make sure your ORACLE_HOME set to Oracle Management Server home

[code]

[oracle@Server 8430622]$ export ORACLE_HOME=/u01/oracle/product/10.2.0/oms10g/

[oracle@Server 8430622]$ opatch apply

Invoking OPatch 10.2.0.3.0

Oracle interim Patch Installer version 10.2.0.3.0

Copyright (c) 2005, Oracle Corporation.  All rights reserved..

Oracle Home       :
/u01/oracle/product/10.2.0/oms10g

Central Inventory : /u01/oracle/oraInventory

from           : /etc/oraInst.loc

OPatch version    :
10.2.0.3.0

OUI version       :
10.2.0.3.0

OUI location      :
/u01/oracle/product/10.2.0/oms10g//oui

Log file location :
/u01/oracle/product/10.2.0/oms10g/cfgtoollogs/opatch/opatch2011-05-17_11-41-29AM.log

ApplySession applying interim patch ‘8430622’ to OH ‘/u01/oracle/product/10.2.0/oms10g’

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Backing up files and inventory (not for auto-rollback) for the Oracle Home

Backing up files affected by the patch ‘8430622’ for restore. This might take a while…

Backing up files affected by the patch ‘8430622’ for rollback. This might take a while…

Patching component oracle.sysman.top.oms, 10.2.0.3.0…

Updating jar file
"/u01/oracle/product/10.2.0/oms10g/sysman/jlib/emagentSDK.jar" with "/sysman/jlib/emagentSDK.jar/oracle/sysman/eml/sec/util/RootCert.class"

ApplySession adding interim patch ‘8430622’ to inventory

Verifying the update…

Inventory check OK: Patch ID 8430622 is registered in Oracle Home inventory with proper meta-data.

Files check OK: Files from Patch ID 8430622 are present in Oracle Home.

OPatch succeeded.

[oracle@Server 8430622]$

[/code]

Now, stop Oracle Management Service process:

[code]

[oracle@Server 8430622]$ cd
/u01/oracle/product/10.2.0/oms10g/opmn/bin

[oracle@Server bin]$ ./opmnctl stopall

opmnctl: stopping opmn and all managed processes…

[oracle@Server bin]$

[/code]

Now, re-secure the management service:

[code]

[oracle@Server oms10g]$ cd $ORACLE_HOME/bin

[oracle@Server bin]$ ./emctl secure oms -reset

Oracle Enterprise Manager 10g Release 3 Grid Control

Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.

Enter Enterprise Manager Root Password :

Enter Agent Registration password :

OPMN processes already stopped…   Done.

Securing central oms…  Started.

Checking Repository…  Done.

Checking Em Key…  Done.

Checking Repository for an existing Enterprise Manager Root Key…

WARNING! An Enterprise Manager Root Key already exists in

the Repository. This operation will replace your Enterprise Manager Root Key.

All existing Agents that use HTTPS will need to be

reconfigured if you proceed. Do you wish to continue and

overwrite your Root Key

(Y/N) ?

Y

Are you sure ? Reset of the Enterprise Manager Root Key

will mean that you will need to reconfigure each Agent

that is associated with this OMS before they will be

able to upload any data to it. Monitoring of Targets

associated with these Agents will be unavailable until

after they are reconfigured.

(Y/N) ?

Y

Generating Enterprise Manager Root Key (this takes a minute)…   Done.

Fetching Root Certificate from the Repository…   Done.

Generating Registration Password Verifier in the Repository…   Done.

Generating Oracle Wallet Password for Enterprise Manager OMS…   Done.

Generating Oracle Wallet for Enterprise Manager OMS…   Done.

Generating Oracle Wallet for iAS HTTP Server…   Done.

Updating HTTPS port in emoms.properties file…   Done.

Generating HTTPS Virtual Host for Enterprise Manager OMS…   Done.

Securing central oms…  Ended.

[/code]

[oracle@Server bin]$

Now start the Oracle Management Service

[code]

[oracle@Server bin]$ ./emctl start oms

Oracle Enterprise Manager 10g Release 3 Grid Control

Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.

opmnctl: opmn is already running

Starting HTTP Server …

Starting Oracle Management Server …

Checking Oracle Management Server Status …

Oracle Management Server is Up.

[oracle@Server bin]$

[/code]

Now switch to the windows where you got the error, click on Retry button.

After all, we got the following screen which tells us that the Grid Control installed successfully: