OMSPatcher Failed To Establish JMX Connection To Weblogic Server. (Doc ID 2642945.1)

Last updated on MARCH 11, 2020

Applies to:

Symptoms

OMS patch 30172893 analyze executed
./omspatcher apply <DIR>/30172893 -analyze OMSPatcher.OMS_DISABLE_HOST_CHECK=true

Analyze failed with

OMSPatcher failed to establish JMX connection to weblogic server. This could be because of one (or) more of the following reasons:
1. Weblogic admin server URL that manages OMS application may not be right.
2. Weblogic admin server credentials (username, password) may not be right.
3. Virtual host configuration. If OMS, weblogic server are on virtual host configuration, Please make sure to add OMSPatcher.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: <MW_HOME>/OMSPatcher/omspatcher apply <DIR>/30172893 -analyze OMSPatcher.OMS_DISABLE_HOST_CHECK=true -invPtrLoc <MW_HOME>/oraInst.loc OMSPatcher.OMS_DISABLE_HOST_CHECK=true)

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.