My Oracle Support Banner

opatchauto Fails With Error Code 231 And Message 'opatchauto failed to establish JMX connection to weblogic server' (Doc ID 1904170.1)

Last updated on NOVEMBER 08, 2019

Applies to:

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


Applying patch 17233019 to the EM Cloud Control OMS fails with the following error:

[ Error during Get weblogic Admin Server information Phase]. Detail: opatchauto was not able to find right interview inputs.
opatchauto failed:
opatchauto 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 is on virtual host configuration, Please make sure to add OPatchAuto.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /var/opt/apps/oemapp/oem12103/Middleware/oms/OPatch/opatchauto apply -invPtrLoc /var/opt/apps/oemapp/oem12103/Middleware/oms/oraInst.loc OPatchAuto.OMS_DISABLE_HOST_CHECK=true)
Please check above conditions and if error persists, Please contact Oracle support.

Log file location: .../Middleware/oms/cfgtoollogs/opatchauto/17233019/opatch_oms_<timestamp>_deploy.log

Recommended actions: Please correct the interview inputs and run opatchauto again.

opatchauto failed with error code 231


From .../Middleware/oms/cfgtoollogs/opatch/<date stamp>_SystemPatch_17233019_1/17233019_ApplyPrereq<timestamp>.log:

[Jun 19, 2014 3:46:00 PM]    {CheckConflictAgainstOracleHome=[ Prerequisite Status: FAILED, Prerequisite output:
                             Summary of Conflict Analysis:
                             There are no patches that can be applied now.
                             Following patches are not required, as they are subset of the patches in Oracle Home or subset of the patches in the given list :
                             Conflicts/Supersets for each patch are:
                             Patch : 17233019
                                 Bug SubSet of 17513525
                                 Subset bugs are:


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

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