Skip Headers
Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 4 (12.1.0.4)

E24089-33
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

J Troubleshooting

This appendix describes how to troubleshoot issues that you might encounter while working with Enterprise Manager Cloud Control.

J.1 Troubleshooting Configuration Assistant Failures

This section describes the log files you must review and the actions you must take when the following configuration assistants fail:

J.1.1 Plugins Prerequisite Check Configuration Assistant

Log Files

Review the following log files:

  • $<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

  • $<OMS_HOME>/cfgtoollogs/pluginca/configplugin_prereq_check_<timestamp>.log

Workaround Steps

  1. Run the plug-ins prerequisite check configuration assistant:

    $<OMS_HOME>/oms/bin/pluginca -action prereqCheck -oracleHome <oms_home_path> -middlewareHome <middleware_home_path> -plugins <plugin_id>=<plugin_version>

    Note:

    For multiple plug-ins, separate the plug-in details with a comma. For example, -plugins <plugin_id>=<plugin_version>, <plugin_id>=<plugin_version>
  2. Complete the installation:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

J.1.2 Repository Configuration Assistant

Log Files

Review the following log files:

  • $<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

  • $<OMS_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

Note:

<ACTION> refers to any of the schema actions, for example, CREATE, TRANSX, MY_ORACLE_SUPPORT, and so on.

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Clean up the Management Repository by running the following command:

    $<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -action drop -dbUser <repository_database_user> -dbPassword <repository_database_password> -dbRole <repository_database_user_role> -mwHome <middleware_home> -mwOraHome <oms_oracle_home> -oracleHome <oms_oracle_home>

    Note:

    • For Microsoft Windows, invoke RepManager.bat.

    • For information on the support for -action drop and -action dropall, see Table 2-3.

  3. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.3 Repository Out Of Box Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

Workaround Steps

  1. Resolve the cause of the issue.

    Caution:

    Do NOT clean up or drop the Management Repository.
  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.4 MDS Schema Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

For more information, review the following log files:

  • <OMS_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/mds.log

  • $<OMS_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/rcu.log

Workaround Steps

Follow these steps:

  1. Drop the MDS schema by running the following command from the OMS home:

    $<OMS_HOME>/sysman/admin/emdrep/bin/mdsschemamanager.pl -action=-dropRepository -connectString=<database_connect_string> -dbUser= <database_user> -dbPassword=<database_password> -oracleHome=<OMS_oracle_home> -mwHome=<middleware_home>

    Where <database_connect_string> must be in the following format:<database_host>:<database_port>:<database_sid>

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.5 OMS Configuration Assistant

Log Files

Review the following log files:

  • If the installer fails BEFORE the OMS configuration assistant starts running, then review the following log file:

    $<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

  • If the installer fails AFTER the OMS configuration assistant starts running, then review the following log file:

    $<OMS_HOME>/cfgtoollogs/omsca/omsca_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Check whether any Java processes are running from the Middleware home. To do so, run the following command from the host where the OMS is running:

    ps -ef | grep java | grep <Oracle_Middleware_Home>

  2. Kill all the running processes, except for installer-related Java processes, by running the following command. The installer-related Java processes run from the temp directory, so you can ignore the processes from that directory.

    kill -9 <process_id>

  3. Remove the Oracle Management Service Instance Base by running the following command:

    rm -rf <OMS_Instance_Home>

  4. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.6 Plugins Deployment and Configuration Configuration Assistant

Log Files

Review the following log files:

  • $<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

  • $<OMS_HOME>/cfgtoollogs/pluginca/configplugin_deploy_<timestamp>.log

Workaround Steps

Complete the plug-ins deployment and configuration, and the installation:

$<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

J.1.7 Start Oracle Management Service Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Run the following command:

$<OMS_HOME>/bin/emctl start oms

J.1.8 Plugins Inventory Migration Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.9 Oracle Configuration Manager Repeater Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.10 OCM Configuration for OMS Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.11 Agent Configuration Assistant

Log Files

Review the following log files:

  • $<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

  • If secure fails, then review the following log file:

    $<AGENT_INSTANCE_HOME>/sysman/log/secure.log

  • In the log file, search for the following statement:

    SEVERE:Plugin configuration has failed.

    If you find this statement, then review the following log file:

    $<AGENT_INSTANCE_HOME>/install/logs/agentplugindeploy_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

    If you are installing in silent mode, then run the following command from the Management Agent home:

    $<AGENT_HOME>/sysman/install/agentDeploy.sh AGENT_BASE_DIR=<agent_base dir_path> OMS_HOST=<oms_host_name> EM_UPLOAD_PORT=<oms_upload_https_port> AGENT_REGISTRATION_PASSWORD=<agent_reg_password> -configOnly

    Note:

    Enter the HTTPS port (secure port) for the EM_UPLOAD_PORT argument.

J.1.12 Agent Upgrade Configuration Assistant

Log Files

If the agent upgrade configuration assistant fails, then review the following log file:

$<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Resolve the cause of the issue, and rerun the configuration assistant from the Jobs page of the Enterprise Manager Cloud Control console.

Note:

The Jobs page referred to here is the page within the earlier release of the Enterprise Manager Cloud Control console.

J.1.13 Repository Upgrade Configuration Assistant

Log Files

Review the following log files:

$<OMS_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

$<OMS_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

Note:

(<ACTION> refers to any of the schema actions, for example, PREUPGRADE, UPGRADE, TRANSX, and so on.)

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.14 Stopping APM Engines Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.1.15 Stop Admin Server Configuration Assistant

Log Files

Review the following log file:

$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

Workaround Steps

Follow these steps:

  1. Resolve the cause of the issue.

  2. Rerun the configuration assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Cloud Control Installation Wizard and click Retry.

    If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If you are installing in silent mode, then rerun the runConfig.sh script (runConfig.bat on Microsoft Windows) from the OMS home:

    $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<oms_home_path> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

    If the runConfig.sh script fails, then clean up your environment and redo the installation.

    Note:

    For Microsoft Windows, run runConfig.bat.

J.2 Troubleshooting ADP and JVMD Failures

This section describes how to troubleshoot the errors encountered while deploying ADP/JVMD Engines, and ADP/JVMD Agents:

J.2.1 ADP Engine Name Conflict

Error

When you deploy ADP Engine to an existing managed server whose instance (for example: EMGC_ADPENGINE2) has not been completely removed, then the new deployment of ADP Engine with the same name fails on the unzip step with the following error:

@ Are you sure you haven't deployed adp engine to a managed server with name  
@ <ADP_managed_server> already?

Workaround Steps

To remove the existing managed server completely, perform the following steps:

  1. Follow the steps listed in Chapter 23 to remove the ADP Engine application and the managed server to which the ADP application is deployed.

  2. Connect to the host machine where the managed server was present, and navigate to the following location to manually delete the managed server (EMGC_ENGINE2):

    $DOMAIN_HOME/<ADP_managed_server>
    
    Where, $DOMAIN_HOME is the location of the Cloud Control domain
    

J.2.2 ADP Agent Deployment Failure

Error

While deploying the ADP Agent, the deployment job may fail on the Deploy ADP Agent On Target step, with the following error:

Failed to connect to https://<host>:<port>/HttpDeployer/HttpDeployerServlet

Also, if you check the output of the Deploy HttpDeployer OnTarget (the previous step), then you will see a message as follows:

Operation is pending and will be activated or cancelled when the ongoing edit session is activated or cancelled.

Workaround Steps

To correct this error, perform the following steps:

  1. Log into WebLogic Administration Console of the domain where the ADP Agent was to be deployed.

  2. On the Administration home page, click Save Changes or Discard Changes, and start deploying the ADP Agent afresh.

J.2.3 ADP Agent Deployment Failure on WebLogic Server 12.1.2

Error

ADP Agent deployment fails on a 12.1.2 WebLogic Server target.

Workaround Steps

Build wlfullclient.jar on the WebLogic Server target where you want to deploy the ADP Agent, and retry the ADP Agent deployment.

For information on how to build wlfullclient.jar, see Oracle Fusion Middleware Developing Stand-alone Clients for Oracle WebLogic Server.

J.2.4 JVMD Agent Deployment Failure

Error

While deploying a JVMD Agent on a target, the Deploy HTTPDeployer On Target job step fails due to an SSL handshake failure. This error may occur if the appropriate patch is not applied on the WebLogic Server software.

Workaround Steps

Apply the appropriate patch on your Oracle WebLogic Server software, then retry the deployment. The appropriate patches for different versions of Oracle WebLogic Server are mentioned in Table J-1. Note that if you are deploying a JVMD Agent on Oracle WebLogic Server 9.2.4 or higher, or Oracle WebLogic Server 10.3.2 or higher, you do not need to apply a patch, as the fix is already present in these versions.

Table J-1 Oracle WebLogic Server Patches to be Applied

Oracle WebLogic Server Version Patch to be Applied

9.1.0

Patch 8422724

9.2.0

Patch 9384535

9.2.1

Patch 9032735

9.2.2

Patch 9309512

9.2.3

Patch 8849418

10.0.0

Patch 8422724

10.0.1

Patch 8895699

10.0.2

Patch 8896127

10.3.0

Patch 8715553

10.3.1

Patch 9003716


J.2.5 SSL Handshake Failure During Agent Deployment

Error

If the WebLogic Domain is SSL enabled using a demo certificate, then the agent deployment may fail due to an SSL Handshake Failure. The following error normally occurs because the demo certificate is not present in AgentTrust.jks:

Certificate chain received from myhost.acme.com - 123.34.11.11 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.

Note: If the WebLogic Domain is using a production certificate, then this issue will not occur as AgentTrust.jks has trusted certificates from all well known CA's.

Workaround Steps

To correct the error, import WebLogic demo certificate to Management Agent keystore as follows:

  1. Export WebLogic Demo certificate from cacerts file. This file is present under the WebLogic home of the Middleware installation at the following location:

    keytool -export -keystore $WEBLOGIC_HOME/server/lib/cacerts -alias certgencab -file mycert.cer

    Press Enter when prompted for a password.

  2. Import WebLogic Demo certificate to TrustStore of Oracle Management Agent as follows:

    keytool -import -keystore $ORACLE_HOME/core/12.1.0.0.0/stage/sysman/config/montrust/AgentTrust.jks -alias wlscertgencab -file mycert.cer

    Enter the password welcome when prompted, and press Enter.

To check if the certificate has been imported correctly, run the following command:

keytool -list -keystore $ORACLE_HOME/core/12.1.0.0.0/stage/sysman/config/montrust/AgentTrust.jks

Where, $ORACLE_HOME is Oracle Management Agent home.

Press Enter when prompted for password, a certificate with the name wlscertgencab is generated with the current date.

J.2.6 Copying ADP Agent Zip or Javadiagnosticagent.ear Failure

Error

If the users who installed the OMS, and the Management Agent are not in the same group, then the job fail on Copying ADP Agent Zip step for an ADP agent, and Copy Javadiagnosticagent Ear step for a JVMD agent, with the following error:

oracle.sysman.emSDK.emd.comm.RemoteOperationException: Error while streaming
JobReader:java.io.IOException: Broken pipe

Workaround Steps

To correct the error, either install the Enterprise Manager Agent using OMS host user credentials.

OR

Enable sudo or Powerbroker settings for the agent host, so that the job runs as if run by an OMS host user.

To set the sudo, or Powerbroker settings, do the following:

  1. In Cloud Control, from the Setup menu, select Security, and then click Privilege Deligation.

  2. On the Manage Privilege Delegation Settings page, do the following:

    1. Select the Sudo or PowerBroker from the type menu.

    2. Enter the host name, or alternatively select the name from the list of host targets. Ensure that the host selected corresponds to the Management Agent; this agent must be the one monitoring the WebLogic Domain where the ADP/JVMD agents have to be deployed.

    3. Click Go.

J.2.7 JVM Pool Creation Failure

Error

No JVM target or pool is created even though the JVMD Agent deployment was successful.

Troubleshooting Tips

The causes of this error may be the following:

  • The JVMD Engine, to which the JVMD Agent connects is down.

    Restart the JVMD Engine and refresh the Application Performance Management pages to check if the target or pool has been created.

  • The user that submitted the job may not have write permissions in the temporary directory of the WebLogic installation.

    Grant the user write permissions for the temporary directory and retry the deployment, or retry the deployment using a different user account.

  • The JVMD Engine host and port are not reachable from the host where the JVMD Agent is deployed.

    Contact the network administrator to resolve the network issue. If a firewall is configured, ensure that the JVMD Engine port is open over the configured firewall.

  • The status of the JVMD Agent deployment is falsely marked as Successful.

    Carefully examine each of the job steps of the JVMD Agent deployment to ensure that there are no unidentified errors or exceptions that led to a false status.

J.3 Troubleshooting Package-Related Issues

While installing Enterprise Manager Cloud Control, you might see the following error message:

Lin.X64 SUSE 10 : Backup fails with the given below error 
install_driver(Oracle) failed: Attempt to reload DBD/Oracle.pm aborted. 
Compilation failed in require at (eval 15) line 3. 

If you see this error, then install the following packages, and try again.

  • libaio-32bit-0.3.104-14.2

  • libaio-devel-32bit-0.3.104-14.2

J.4 Troubleshooting Deinstallation Failures

While deinstalling the Shared Agent as described in Section 22.1.2.4, you might see the following error:

SEVERE:The home <AGENT_HOME> cannot be deinstalled. Please deinstall all referenced home(s) <REFERENCE_HOME>

For example,

SEVERE:The home /tmp/agt_install/core/12.1.0.1.0 cannot be deinstalled. Please deinstall all referenced home(s) /tmp/agt_install/plugins

If you see the error, then deinstall the Shared Agent following these steps:

  1. Identify the dependent plug-ins and the sbin home to be detached from the Central Inventory:

    1. On the host where the Shared Agent is installed, open the following file from the Central Inventory:

      <absolute_path>/oraInventory/ContentsXML/inventory.xml

    2. Make a note of the dependent plug-ins listed within the <REFHOMELIST> and </REFHOMELIST> tags.

      For example,

      <HOME NAME="nfs5515" LOC="/home/john/software/oracle/agent/core/12.1.0.0.0" TYPE="O" IDX="1">
      <REFHOMELIST>
      <REFHOME LOC="/home/john/software/oracle/agent/plugins/oracle.sysman.oh.discovery.plugin_12.1.0.0.0"/>
      <REFHOME LOC="/home/john/software/oracle/agent/plugins/oracle.sysman.db.discovery.plugin_12.1.0.0.0"/>
      <REFHOME LOC="/home/john/software/oracle/agent/plugins/oracle.sysman.emas.discovery.plugin_12.1.0.0.0"/>
      <REFHOME LOC="/home/john/software/oracle/agent/plugins/oracle.sysman.oh.agent.plugin_12.1.0.0.0"/>
      </REFHOMELIST>
      </HOME>  
      
    3. Make a note of the sbin directory listed within the <REFHOMELIST> and </REFHOMELIST> tags.

      For example,

      <HOME NAME="nfs5515" LOC="/home/john/software/oracle/agent/core/12.1.0.0.0" TYPE="O" IDX="1">
      <REFHOMELIST>
      <REFHOME LOC="home/john/software/oracle/agent/sbin"/>
      </REFHOMELIST>
      
    4. Detach the dependent plug-ins you identified in Step 1 (b) from the Central Inventory. To do so, run the following command from the Master Agent home that is visible on the host where your Shared Agent is installed:

      $<AGENT_HOME>/oui/bin/runInstaller -detachHome -silent -waitForCompletion -invPtrLoc <absolute_path>/oraInst.loc ORACLE_HOME=<plug-in_home> -nogenerateGUID

      For example,

      /home/john/software/oracle/agent/core/12.1.0.3.0/oui/bin/runInstaller -detachHome -silent -waitForCompletion -invPtrLoc /home/john/software/oracle/agent/core/12.1.0.3.0/oraInst.loc ORACLE_HOME=/home/john/software/oracle/agent/plugins/oracle.sysman.emas.discovery.plugin_12.1.0.3.0 -nogenerateGUID

      Note:

      This step detaches only one plug-in at a time. Therefore, if you have multiple plug-ins, repeat this step to detach every other dependent plug-in.
    5. Detach the sbin home you identified in Step 1 (c) from the Central Inventory. To do so, run the following command from the Master Agent home that is visible on the host where your Shared Agent is installed:

      $<AGENT_HOME>/oui/bin/runInstaller -detachHome -silent -waitForCompletion -invPtrLoc <absolute_path>/oraInst.loc ORACLE_HOME=<sbin_home> -nogenerateGUID

      For example,

      /home/john/software/oracle/agent/core/12.1.0.3.0/oui/bin/runInstaller -detachHome -silent -waitForCompletion -invPtrLoc /home/john/software/oracle/agent/core/12.1.0.3.0/oraInst.loc ORACLE_HOME=/home/john/software/oracle/agent/sbin -nogenerateGUID

  2. Deinstall the Shared Agent. To do so, run the following command from the Master Agent home that is visible on the host where your Shared Agent is installed:

    $<AGENT_HOME>/perl/bin/perl <AGENT_HOME>/sysman/install/NFSAgentDeInstall.pl AGENT_INSTANCE_HOME=<absolute_path_to_agent_instance_home> ORACLE_HOME=<absolute_path_to_agent_home>

    For example,

    /home/john/software/oracle/agent/core/12.1.0.3.0/perl/bin/perl /home/john/software/oracle/agent/core/12.1.0.3.0/sysman/install/NFSAgentDeInstall.pl AGENT_INSTANCE_HOME=/home/john/software/oracle/agent/agent_inst ORACLE_HOME=/home/john/software/oracle/agent/core/12.1.0.3.0

J.5 Troubleshooting Management Agent Installation Failures

While deploying a Management Agent, you may encounter the following failures:

  • If the Management Agent installation fails, and the Management Agent deployment logs available at <ORACLE_HOME>/cfgtoollogs/agentDeploy/agentDeploy<TIMESTAMP>.log mention that the port check failed, then run the agentDeploy.sh script again, using the -ignorePrereqs option.

    Also, if the port check failed for a host that has an IPv6 address listed as part of the host DNS setup, then ensure that the IPv6 address is enabled on the host.

  • If the Management Agent installation fails on a Microsoft Windows host, with an error message mentioning that setup.exe cannot be executed, then log in using an administrator account and retry the Management Agent installation on the host.