In this Document

Applies to:

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.

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.

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:

The Apache Web server log will report error (28750) as follows:

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.

1. 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.
2. 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
3. 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
4. Re-start Oracle Management Service by executing the following command:
   
   
   /bin/emctl start oms
5. Retry the failed step from the error dialog to complete the installation.  

        8430622补丁已作为附件上传p8430622_10203_GENERIC.zip

[oracle1@dg1 bin]$ ./emctl upload

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.  

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

---------------------------------------------------------------

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

这个错误困扰了我2天，终于让我找到了如下文章：

Communication: Agent to OMS Communication Fails if the Agent is 'Blocked' in the 10.2.0.5 Grid Console (文档 ID 799618.1) 
修改时间:2012-9-6类型:PROBLEM状态:PUBLISHED优先级:3 

In this Document
  Symptoms
  Cause
  Solution
  References

---

APPLIES TO:

Enterprise Manager Base Platform. - Version: 10.2.0.5 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.
Enterprise Manager Grid Control - Version: 10.2.0.5 and later? ? ? [Release: 10.2 and later ]

SYMPTOMS

After upgrading the OMS and Agent to 10.2.0.5 version, getting the following error in /sysman/log/emagent.trc:

Did not receive valid response to ping "ERROR-Agent is blocked. Blocked reason is: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console. Please contact EM adminstrator to unblock the agent"

The command: emctl upload agent
fails with:

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

The Agent can however be secured successfully with the OMS. 

CAUSE

The Agent Re-synchronisation is a new feature in 10.2.0.5 Grid Control which verifies whether an Agent that been uploading earlier to the OMS is re-installed or restored from a backup. If yes, the OMS blocks further updates from this Agent until the information about the Agent and all its targets are synchronized between the Repository and the Agent.

Factors which can cause the Agent to go out-of-sync with the Repository:

1. Agent is re-installed or restored from a backup, on the same port number as before.
2. The /sysman/emd/agntstmp.txt is manually deleted for some reason.

SOLUTION

To solve the issue you have to perform. following from grid console 

+ Login to 10.2.0.5 Grid Console as sysman user 

+ Navigate to Setup -> Agents -> Click on problematic Agent name 

+ In Agent home page click on "Resynchronize" Button on right hand top of the page. 
Choose the 'Unblock Agent' option and click Continue

Ensure that the Agent is up and running when attempting the Resynchronization.

Once the re-synchronization is completed successfully, the Agent should be able to communicate with the OMS.

Sometimes, the re-synchronization may complete with results such as:

Agent Operation completed with errors. For those targets that could not be saved, please go to the target's monitoring configuration page to save them. All other targets have been saved successfully. Agent has not been unblocked.

1. Error saving target database1.domain:oracle_database - Skipping target {database1.domain, oracle_database}: Missing properties - UserName, password
2. Error saving target database2.domain:oracle_database - Skipping target {database2.domain, oracle_database}: Missing properties - UserName, password
...
OR

Error saving target EnterpriseManager0.omsmachine.domain_Web 
Cache:oracle_webcache - Skipping target 
{EnterpriseManager0.omsmachine.domain_Web Cache, oracle_webcache}: 
Missing properties - authpwd, authuser

The above indicates that the Repository has been unable to completely save the details of the all targets that the Agent currently has. In this case, the Agent was re-installed and has newly discovered all the Database targets and iAS targets, which are not completely configured as yet i.e the monitoring password is missing. To resolve the above:

-  Navigate to the Agent home page in the Grid Console. Choose one database at a time and click on the 'Configure' button.
- In the Monitoring Configuration page, enter the password for the monitoring user and save.
- Perform. the same for any other target that is shown in the result from the Agent re-synchronization.
- Once, all the targets are configured in this manner go to Setup -> Agents -> choose this Agent name and click on the 'Unblock' button.

REFERENCES

NOTE:416898.1 - Agent Upload to OMS Fails if Multiple Agents are Installed and Targets are Discovered as Duplicates in the Grid Console
NOTE:1307816.1 - Right After Install, the Grid Control Agent Generates ERROR-Agent is blocked. Blocked reason is: Agent is out-of-sync with repository 

        根据文章的描述，问题得到解决。

omsca_01.jpg