When installing Oracle Enterprise Manager 10.2.0.3.0 after 31 december 2010 you can expect the following error during installation on step: OMS configurations. This error comes from the expiration of a certificate on OEM. For more information see Metalink Note: 1228103.1.
Logfile installActions2011-01-31_10-49-54-AM.log:
INFO: Created a new file /u00/oracle/product/10.2.0/oms10g/cfgtoollogs/configToolFailedCommands INFO: Since the option is to overwrite the existing /u00/oracle/product/10.2.0/oms10g/cfgtoollogs/configToolFailedCommands file, backing it up INFO: The backed up file name is /u00/oracle/product/10.2.0/oms10g/cfgtoollogs/configToolFailedCommands.bak INFO: Created a new file /u00/oracle/product/10.2.0/agent10g/cfgtoollogs/configToolFailedCommands INFO: Since the option is to overwrite the existing /u00/oracle/product/10.2.0/agent10g/cfgtoollogs/configToolFailedCommands file, backing it up INFO: The backed up file name is /u00/oracle/product/10.2.0/agent10g/cfgtoollogs/configToolFailedCommands.bak SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration assistants at this time. Not successfully running any "Recommended" assistants means your system will not be correctly configured. 1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures. 2. Fix the errors causing these failures. 3. Select the failed assistants and click the 'Retry' button to retry them. INFO: User Selected: Yes/OK
When starting OPMN by hand you get the error below:
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=ysoms01:6200
4 of 5 processes started.
ias-instance id=EnterpriseManager0.ysoms01.hosting.yenlo.nl
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
HTTP_Server/HTTP_Server/HTTP_Server
Error
--> Process (pid=21810)
failed to start a managed process after the maximum retry limit
Log:
/u00/oracle/product/10.2.0/oms10g/opmn/logs/HTTP_Server~1
In the log file mentioned you find noting, but when you look in the error log of Apache, you’ll see the following error:
[Mon Jan 31 11:49:43 2011] [error] mod_ossl: Init: Server ysoms01:1159: SSL setup failed: call to nzos_OpenWallet returned error 28750 [Mon Jan 31 11:49:43 2011] [error] mod_ossl: Unknown error
Steps to resolve this issue.
Don’t quite the installer.
Download patch 8430622. And take the actions described below:
Stop the OMS:
[oracle@ysoms01 8430622]$ 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@ysoms01 8430622]$ opmnctl stopall opmnctl: stopping opmn and all managed processes...
After unzipping, apply the patch to the OMS home:
[oracle@ysoms01 8430622]$ /u00/oracle/product/10.2.0/oms10g/OPatch/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 : /u00/oracle/product/10.2.0/oms10g Central Inventory : /u00/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.3.0 OUI version : 10.2.0.3.0 OUI location : /u00/oracle/product/10.2.0/oms10g/oui Log file location : /u00/oracle/product/10.2.0/oms10g/cfgtoollogs/opatch/opatch2011-01-31_11-55-36AM.log ApplySession applying interim patch '8430622' to OH '/u00/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 "/u00/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.
Re-secure the Oracle Management Service:
[oracle@ysoms01 8430622]$ 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.
Start OMS:
[oracle@ysoms01 8430622]$ 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.
Press retry in the OUI, the setup will continue.