EM13c: Agent Silent Installation Fails while Validating OMS Host and Port

郑全

EM 12C, EM13c: Enterprise Manager Cloud Control Agent Silent Installation Fails while Validating OMS Host and Port (Doc ID 1368010.1)
In this Document
Symptoms
Cause

Solution
APPLIES TO:
Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.
Checked for relevance on 18-Aug-2013
SYMPTOMS
Enterprise Manager Cloud Control Agent installation using the Silent method fails with the following error:


$ ./agentDeploy.sh AGENT_BASE_DIR=/u01/oracle/agent12c RESPONSE_FILE=/u01/oracle/archives/agent.rsp

AGENT_BASE_DIR=/u01/oracle/agent12c

Validating the OMS_HOST & EM_UPLOAD_PORT
Executing command : /u01/oracle/agent12c/core/12.1.0.0.0/jdk/bin/java -classpath /u01/oracle/agent12c/core/12.1.0.0.0/jlib/agentInstaller.jar:/u01/oracle/agent12c/core/12.1.0.0.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /u01/oracle/agent12c/core/12.1.0.0.0 /u01/oracle/archives /u01/oracle/agent12c -prereq

Validating oms host & port with url: http:// <OMS_Hostname>:4890/empbs/genwallet
Validating oms host & port with url: https://  <OMS_Hostname> :4890/empbs/genwallet
Return status:1
ERROR: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid host name and port number for the OMS to successfully deploy the agent.

Alternatively, you can do one of the following:
1. Install the agent software only and configure the agent later once the OMS is available. Installing just the software without configuring can be accomplished by passing the '-softwareOnly' argument to agentDeploy.sh and if windows pass the arguments to agentDeploy.bat instead. Configuring the agent after the software has been installed can be accomplished by passing the '-configOnly' argument to agentDeploy.sh and if platform is windows pass the arguments to agentDeploy.bat.
2. Force the configuration of the agent, even though the OMS is not available. This can be accomplished by passing the '-forceConfigure' option to agentDeploy.sh and if windows pass the arguments to agentDeploy.bat.

NOTE: Forcing the configuration of the agent when the OMS is not available will configure the agent to use HTTP (non-secure) communication. In order to properly establish secure HTTPS communication between the agent and the OMS, you will need to secure the agent after the OMS is available.

Passing the 10.2.0.5.0 or 11.1.0.1.0 OMS_HOST and EM_UPLOAD_PORT then that is not supported. Pass in a valid hostname and port number of 12c OMS.
The following entries are seen in the log file

<Agent_Home>/cfgtoollogs/agentDeploy/agentDeploy_<Timestamp>.log

INFO: Validating oms host & port with url: https://<OMS_Hostname>:4890/empbs/genwallet
SEVERE: Connection refusedNo route to host
INFO: Validating oms host & port with url: http://<OMS_Hostname>:4890/empbs/genwallet
SEVERE: Connection refusedNo route to host ret 1
SEVERE: ERROR: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available.  Pass in a valid host name and port number for the OMS to successfully deploy the agent.

  Alternatively, you can do one of the following:
    1. Install the agent software only and configure the agent later once the OMS is available.  Installing just the software without configuring can be accomplished by passing the '-softwareOnly' argument to agentDeploy.sh and if windows pass the arguments to  agentDeploy.bat instead.  Configuring the agent after the software has been installed can be accomplished by passing the '-configOnly' argument to agentDeploy.sh and if platform is windows pass the arguments to  agentDeploy.bat.
     2. Force the configuration of the agent, even though the OMS is not available.  This can be accomplished by passing the '-forceConfigure' option to agentDeploy.sh and if windows pass the arguments to  agentDeploy.bat.  

NOTE:  Forcing the configuration of the agent when the OMS is not available will configure the agent to use HTTP (non-secure) communication.  In order to properly establish secure HTTPS communication between the agent and the OMS, you will need to secure the agent after the OMS is available.

If you are passing 10.2.0.5.0 or 11.1.0.1.0 OMS_HOST and EM_UPLOAD_PORT then that is not supported. Pass in a valid hostname and port number of 12c OMS.
SEVERE:
ERROR: Agent Deployment Failed
CAUSE
The installation might fail for the following reasons:

1) OMS is not accessible with the port mentioned in EM_UPLOAD_PORT
2) OMS might be down.
3) Agent machine is not able to communicate with OMS machine.



SOLUTION


1) OMS should be up and running, so check the status of the OMS using the following:
<OMS_HOME>/bin/emctl status oms

Sample Output
$ ./emctl status oms
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up

2) ping <OMS_Hostname>

Sample Output
$ ping   <OMS_Hostname>  
PING   <OMS_Hostname>   (<IPAddress>) 56(84) bytes of data.
64 bytes from   <OMS_Hostname>  (<IPAddress>): icmp_seq=1 ttl=64  ime=0.053 ms
64 bytes from   <OMS_Hostname>   (<IPAddress>): icmp_seq=2 ttl=64 time=0.034 ms

3) From Agent machine, execute the below

wget http://<OMS_Hostname>:<EM_UPLOAD_PORT>/empbs/genwallet
or
wget https://<OMS_Hostname>:<EM_UPLOAD_PORT>/empbs/genwallet

      Anyone of the above should be able to connected to OMS machine.

Example:
---------
http:// <OMS_Hostname> :4890/empbs/genwallet
or
https:// <OMS_Hostname> :4890/empbs/genwallet

Sample Output
$ wget http:// <OMS_Hostname> :4890/empbs/genwallet
--2011-10-16 23:05:21-- http:// <OMS_Hostname> :4890/empbs/genwallet
Resolving  <OMS_Hostname> ... <IPAddress>
Connecting to  <OMS_Hostname> |<IPAddress>|:4890... connected.
HTTP request sent, awaiting response...
200 OK
Length: 173 [text/html]
Saving to: `genwallet'

100%[======================================>] 173 --.-K/s in 0s

2011-10-16 23:08:13 (11.1 MB/s) - `genwallet' saved [173/173]

4) Once the above resolved, then Retry the installation again.