EM 12c: Enterprise Manager 12 Cloud Control Additional OMS Installation Fails with Message: ERROR: exception encountered while checking duplicate OMS name (Doc ID 1952449.1)

Last updated on DECEMBER 13, 2014

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.3.0 and later
Information in this document applies to any platform.

Symptoms

Additional OMS installation fails with the recovery command during OMS configuration with this message:


omsca recover -ms -backup_file /opt/oracle/admin/sw/opf_ADMIN_20141124_085307.bka -AS_HTTPS_PORT 7101 -MSPORT 7202 -MS_HTTPS_PORT 7301 -EM_NODEMGR_PORT 7403 -EM_UPLOAD_PORT 4889 -EM_UPLOAD_HTTPS_PORT 4900 -EM_CONSOLE_PORT 7788 -EM_CONSOLE_HTTPS_PORT 7799 -config_home /opt/oracle/product/gc_inst -EM_INSTANCE_HOST <host name>.com
.
ERROR: exception encountered while checking duplicate OMS name

 

From the .../Middleware/oms/cfgtoollogs/omsca/omsca<>.log:

OMSCA-ERR:Connection to Admin server failed. Please check the admin server credentials and ensure admin server is up and running.
ERROR: exception encountered while checking duplicate OMS name
null
OMSCA-ERR:Exception encountered. Check the trace file:/opt/oracle/product/middleware/oms/cfgtoollogs/omsca/omsca_20141203080452.log
java.lang.NullPointerException
       at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.execCmd(OMSWLSAdapter.java:3929)
       at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.execCmd(OMSWLSAdapter.java:3894)
       at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.adapterDeleteOMS(OMSWLSAdapter.java:1915)
       at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.adapterCleanup(OMSWLSAdapter.java:4138)
       at oracle.sysman.omsca.framework.OMSCARecoveryConfig.execute(OMSCARecoveryConfig.java:694)
       at oracle.sysman.omsca.framework.OMSConfigAssistantDriver.main(OMSConfigAssistantDriver.java:240)
OMS CA recover failed

 

from the .../gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.log:

SEVERE: WLSAdminServer::Failed to get Admin server connection
java.io.IOException
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
at oracle.sysman.omsca.adapter.wls.WLSAdminServer.initConnection(WLSAdminServer.java:147)
at oracle.sysman.omsca.adapter.wls.WLSAdminServer.<init>(WLSAdminServer.java:95)
at oracle.sysman.omsca.adapter.wls.WLSServer.<init>(WLSServer.java:76)
at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.dupOMSCheck(OMSWLSAdapter.java:5095)
at oracle.sysman.omsca.framework.OMSCARecoveryConfig.execute(OMSCARecoveryConfig.java:667)
at oracle.sysman.omsca.framework.OMSConfigAssistantDriver.main(OMSConfigAssistantDriver.java:240)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://<hostname>.com:7101: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination]

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms