| 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] |  To Bottom |  |
| Modified:30-May-2013Type:BULLETINStatus:PUBLISHEDPriority:3 |
|
In this Document
| Purpose |
| Scope |
| Details |
| References |
Applies to:
Enterprise Manager Base Platform. - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]Information in this document applies to any platform.
Purpose
What is the Issue?
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.
Scope
What Releases Are Affected?
Errors will occur when installing the following Enterprise Manager Grid Control 10g base releases on or after 31-Dec-2010.
| Base Release | Supported Operating Systems |
|---|---|
| 10.2.0.1.0 | ■ Linux x86 ■ HP-UX PA-RISC (64-bit) ■ Solaris SPARC (64-bit) ■ AIX 5L (64-bit) |
| 10.2.0.1.1 | ■ Solaris SPARC (64-bit) |
| 10.2.0.2.0, 10.2.0.2.1 | ■ Windows x86 |
| 10.2.0.3.0 | ■ Linux x86-64 ■ HP-UX Itanium |
What Releases Are NOT Affected?
You will not encounter issues related to certificate expiration when installing the following Enterprise Manager Grid Control 10g releases. In these releases, the certificate expiration date is set to 10 years after the date of installation.
| Release | Supported Operating Systems |
|---|---|
| 10.2.0.1.1 | ■ Linux x86 |
Details
What Happens During the Installation Failure?
The installation will fail at the “OMS Configuration” step with the following error:
The opmn.log will report the following errors, indicating that Oracle Management Service failed to start:
'
FINE: oracle.sysman.emCfg.logger.CfmLogger: log: oracle.sysman.top.oms:PerformSecureCommand:runCmd:Command
Output stderr:
'
================================================================================
opmn id=host1.example.com:6201
5 of 6 processes started.
ias-instance id=EnterpriseManager1.host1.example.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ias-component/process-type
/process-set:
HTTP_Server/HTTP_Server/HTTP_Server
Error
--> Process (pid=18346)
failed to start a managed process after the maximum retry limit
Log:
/scratch/caexptest/oms10g/opmn/logs/HTTP_Server~1
'
FINE: oracle.sysman.emCfg.logger.CfmLogger: log: oracle.sysman.top.oms:OmsPlugIn:Requested Configuration
Step 5 have been completed with status=false
The Apache Web server log will report error (28750) as follows:
failed: call to nzos_OpenWallet returned error 28750
[Wed Jan 5 09:10:28 2011] [error] mod_ossl: Unknown error
[Wed Jan 5 09:10:30 2011] [error] mod_ossl: Init: Server host1.example.com:4898: SSL setup
failed: call to nzos_OpenWallet returned error 28750
[Wed Jan 5 09:10:30 2011] [error] mod_ossl: Unknown error
What Actions Do You Need to Take?
If you encounter errors while installing one of the Enterprise Manager Grid Control 10g base releases noted above on or after 31-Dec-2010, you must perform. the following steps to recover from the installation errors.
- Download and Apply the Patch:8430622 from My Oracle Support to the Oracle Management Service installation. Note that the patch README.txt specified that only the OMS should be stopped for patch application, emctl stop oms. This command will stop the OMS web application and web tier, but leave certain other opmn processes running to support patch application.Important Note: On Windows platforms, the patch would fail to apply with the error:
[...] Patch 8430622: Required component(s) missing : [ oracle.sysman.top.oms, 10.2.0.2.0, higher version 10.2.0.2.1 found. ] [...].
A version of the patch 8430622, specific for Windows platforms is attached to this document.
Please download and apply the patch attached instead of the patch 8430622 available at My Oracle Support.
Note that the OMS should still be stopped to apply the patch. - After applying the patch, stop all of the remaining processes associated with the Oracle Management Service (OMS) with the following command:
/opmn/bin/opmnctl stopall - Re-secure Oracle Management Service with the following command:
/bin/emctl secure oms -reset
You will be prompted twice to confirm that the Root key must be overwritten. In both cases, enter upper-case "Y" as the response. Any other response (including lower-case "y") will cause the command to terminate without completing. If this happens, the command can be re-invoked:$ ./emctl secure oms -reset
Oracle Enterprise Manager 10g Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password : ******
Enter Agent Registration Password : ******
OPMN processes successfully 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 - Re-start Oracle Management Service by executing the following command:
/bin/emctl start oms - Retry the failed step from the error dialog to complete the installation.