OMSPatcher Failed To Establish JMX Connection To Weblogic Server.
(Doc ID 2642945.1)
Last updated on MARCH 11, 2020
Applies to:Enterprise Manager Base Platform - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
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)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document