OMS CA:10.2.0.1.0 GC Install Fails with "Error processing emkey-353131.1-CSDN博客

Problem: OMS CA: 10.2.0.1.0 Grid Control Install Fails with "Error processing emkey command" [ID 353131.1]

In this Document
Symptoms
Cause
Solution
References

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.1
This problem can occur on any platform.

Symptoms

Attempting to install Grid Control 10.2.0.1.0. All required libraries and kernel parameters have been set. The Oracle Universal Installer (OUI) runs the pre-checks and there are no failures. Everything runs fine during the install until the OMS Configuration Assistant (CA) runs. Then it fails with the following error:

INFO: Command = oracle.sysman.emcp.oms.OmsPlugIn -configureOms

Operation Stopping OPMN Processes is in progress.
Operation EM Deploying is in progress.

Operation Unlocking Passwords and Out of Box setup is in progress.

Command = oracle.sysman.emcp.oms.OmsPlugIn has failed

INFO: Configuration assistant "OMS Configuration" failed

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.

Sometimes after using the work around and pressing retry, you will get this next error:

INFO: Starting to execute configuration assistants
INFO: Command = oracle.sysman.emcp.oms.OmsPlugIn -configureOms

Command = oracle.sysman.emcp.oms.OmsPlugIn has failed
Exception : java.lang.Exception: Error processing emkey command config emkey -repos -force from repository =

INFO: Configuration assistant "OMS Configuration" failed

Cause

OUI-25031 is a generic error message. One possible cause for this error could be bug.4755224 OMS CONFIGURATION FAILED DURING INSTALL OF 10.2. GRID.

Solution

The work around for the first error is
1. Edit the listener.ora file add the parameter below:

SUBSCRIBE_FOR_NODE_DOWN_EVENT_=OFF

where would be replaced with the actual listener name configured in the
listener.ora file.

For example, if the listener name is LISTENER (default), the parameter would be:

SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF

2. Save the listener.ora file
3. Stop and restart the listener process
4. Retry the Configuration Assistant in the OUI (Click the retry button)

The workaround for the second error listed above is to edit the listener.ora file again and this time remove the following lines:

(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
)

Then save the file again, bounce the listener, and hit retry again. This time is should complete.