In this Document

Applies to:

Purpose

This Troubleshooting Guide is intended to help diagnose the generic error "oracle.sysman.emcp.agent.AgentPlugIn" that is displayed at stdout when the Agent Configuration Assistant fails to complete successfully.

Troubleshooting Steps

The Agent Configuration Assistant

The Agent Configuration Assistant is launched in one of two ways :

• manually with the command agentca or
• automatically by the Oracle Universal Installer (OUI) when you install a Grid Control Management Agent or when you install a Grid Control Oracle Management Server (OMS) - first Grid Control Installation or Additional OMS Installation. This is because when you install an OMS, there is automatically a chained monitoring Grid Control Management Agent installation performed.

It may happen that the Agent Configuration Assistant fails to complete successfully. In that case the following generic error message is displayed at stdout (Standard Outpout of the tool which launched the Agent Configuration Assistant).

OUI Error Message

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.

Command Line error Message

INFO: Starting to execute configuration assistants
INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn

Performing targets discovery and agent configuration

Command = oracle.sysman.emcp.agent.AgentPlugIn has failed

INFO: Configuration assistant "Agent Configuration Assistant" failed

Examples of Specific Error Messages:

• Exception : java.lang.Exception: 6
• Exception : java.lang.Exception:
• Exception : java.lang.Exception: OPS:Exception while processing cluster node=racnode1. Failed to copy file /u01/app/oracle/product/10.2.0/agent_1/agent10g/racnode2.domain to destination racnode2. ExceptionMessage=PRKC-1002 : All the submitted commands did not execute successfully. Terminating...

The error message "oracle.sysman.emcp.agent.AgentPlugIn has failed" reveals that the Agent Configuration Assistant failed. Oracle Support needs to determine:

1. At which step did the Agent Configuration Assistant fail?
   This will enable us to take the appropriate action once the root cause of the failure is fixed
2. Why did the Agent Configuration Assistant fail?
   This will enable us to fix the root cause in order to have the Agent Configuration Assistant complete successfully.

Agent Configuration Assistant steps performed during Installation

The Agent Configuration Assistant runs with the following parameters provided either interactively by the Universal Installer or silently through a response file or via the command line or computed during the installation phase preceding the launch of the Agent Configuration Assistant:

OMS Hostname
OMS Upload Unsecured Port
OMS Registration Password
Agent Hostname
Agent Port

With this information, the install process:

1. Acknowledges the name of the host
2. Acknowledges the Agent Port
3. Secures the Agent
4. Performs the targets discovery using a temporary file
5. Creates and populates the targets.xml file
6. Starts the agent and uploads the targets metadata to the OMS.

Log and Trace files to check in order to find the Root Cause of the failure

1. Check the OUI Installation log/trace/err files

The OUI installation log files are located in $ORACLE_HOME/cfgtoollogs/oui

The installation log file name is in the format installActionsYYYY-MM-DD_HH-MI-SS-AM/PM.log

The installation log file will show at which step the Configuration Assistant failed and the error returned by the Agent Configuration Assistant.

2. Check the Configuration Assistant log files

The Configuration Assistant log files are located in $ORACLE_HOME/cfgtoollogs/cfgfw

The Configuration Assistant log file to check is in the format oracle.sysman.top.agent_YYYY-MM-DD_HH-MI-SS-AM/PM.log

There are other log files located in $ORACLE_HOME/cfgtoollogs/cfgfw. However these log files are not created by the Agent Configuration Assistant but by other Assistants launched during the installation of the Agent. These log files may also display errors which can explain why the Agent Configuration Assistant failed.

• CfmLogger_YYYY-MM-DD_HH-MI-SS-AM/PM.log
• oracle.sysman.ccr_YYYY-MM-DD_HH-MI-SS-AM/PM.log
  Log File of Oracle Configuration Manager (OCM Collector) Installation
• oracle.sysman.patchset_YYYY-MM-DD_HH-MI-SS-AM/PM.log
  Log File created during Upgrade (Patchset Installation)

3. Check the Agent log and trace files

If the Agent Configuration Assistant fails at the final step (Agent Start), then look for additional information in the Agent Log/Trace files located in $ORACLE_HOME/sysman/log (or $ORACLE_HOME/host/sysman/log in case of installation on a RAC Cluster):

• emagent.nohup
• emagent.log
• emagent.trc

Actions to take in order to successfully complete the Agent Configuration

The actions depend on the Root Cause of the error.

You will find several notes which will help you to fix your specific issue.

The best way to find these notes is to query the knowledge logged to My Oracle Support with the following keywords:

oracle.sysman.emcp.agent.AgentPlugIn

Examples:

oracle.sysman.emcp.agent.AgentPlugIn "Invalid Agent Registration Password"
oracle.sysman.emcp.agent.AgentPlugIn "java.lang.Exception: Failed to allocate port"
oracle.sysman.emcp.agent.AgentPlugIn "java.lang.Exception: 6"
oracle.sysman.emcp.agent.AgentPlugIn agentTZRegion
oracle.sysman.emcp.agent.AgentPlugIn "Host discovery failed"
oracle.sysman.emcp.agent.AgentPlugIn OPS:Exception