12c EM: "OPatchauto apply -analyze" Failed With Error Code 231
(Doc ID 2744499.1)
Last updated on JANUARY 18, 2023
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.5.0 and laterInformation in this document applies to any platform.
Symptoms
12.1.0.5 EM : "OPatchauto apply -analyze" Failed with error code 231
$<OMS_HOME>/OPatch>./opatchauto apply -analyze
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation. All rights reserved.
OPatchauto version : 11.1.0.12.9
OUI version : 11.1.0.13.0
Running from : /<OMS_HOME>
Log file location : /<OMS_HOME>/cfgtoollogs/opatch/opatch2021-01-14_16-06-22PM_1.log
OPatchauto log file: /<OMS_HOME>/cfgtoollogs/opatchauto/31250739/opatch_oms_2021-01-14_16-06-23PM_analyze.log
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 are on virtual host configuration, Please make sure to add OPatchAuto.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /<OMS_HOME>/OPatch/opatchauto apply -analyze -property_file /home/oracle/opatchauto.properties -invPtrLoc /<OMS_HOME>/oraInst.loc OPatchAuto.OMS_DISABLE_HOST_CHECK=true)
Please check above conditions and if error(s) still persist, Please contact Oracle support.
[ 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 are on virtual host configuration, Please make sure to add OPatchAuto.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /<OMS_HOME>/OPatch/opatchauto apply -analyze -property_file /home/oracle/opatchauto.properties -invPtrLoc /<OMS_HOME>/oraInst.loc OPatchAuto.OMS_DISABLE_HOST_CHECK=true)
Please check above conditions and if error(s) still persist, Please contact Oracle support.
Log file location: /orabin/app/oracle/middleware2/oms/cfgtoollogs/opatchauto/31250739/opatch_oms_2021-01-14_16-06-23PM_analyze.log
Recommended actions: Please correct the interview inputs and run opatchauto again.
OPatchauto failed with error code 231
Copyright (c) 2014, Oracle Corporation. All rights reserved.
OPatchauto version : 11.1.0.12.9
OUI version : 11.1.0.13.0
Running from : /<OMS_HOME>
Log file location : /<OMS_HOME>/cfgtoollogs/opatch/opatch2021-01-14_16-06-22PM_1.log
OPatchauto log file: /<OMS_HOME>/cfgtoollogs/opatchauto/31250739/opatch_oms_2021-01-14_16-06-23PM_analyze.log
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 are on virtual host configuration, Please make sure to add OPatchAuto.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /<OMS_HOME>/OPatch/opatchauto apply -analyze -property_file /home/oracle/opatchauto.properties -invPtrLoc /<OMS_HOME>/oraInst.loc OPatchAuto.OMS_DISABLE_HOST_CHECK=true)
Please check above conditions and if error(s) still persist, Please contact Oracle support.
[ 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 are on virtual host configuration, Please make sure to add OPatchAuto.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /<OMS_HOME>/OPatch/opatchauto apply -analyze -property_file /home/oracle/opatchauto.properties -invPtrLoc /<OMS_HOME>/oraInst.loc OPatchAuto.OMS_DISABLE_HOST_CHECK=true)
Please check above conditions and if error(s) still persist, Please contact Oracle support.
Log file location: /orabin/app/oracle/middleware2/oms/cfgtoollogs/opatchauto/31250739/opatch_oms_2021-01-14_16-06-23PM_analyze.log
Recommended actions: Please correct the interview inputs and run opatchauto again.
OPatchauto failed with error code 231
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |