My Oracle Support Banner

EM 13c: Applying an Enterprise Manager13c Cloud Control OMS Patch with omspatcher Fails with Message: error code 231 (Doc ID 2305091.1)

Last updated on SEPTEMBER 13, 2017

Applies to:

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

Symptoms

Enterprise Manager (EM) 13.2 Cloud Control omspatcher fails with error code 231 when applying a patch to the OMS Oracle Home
The WebLogic Server (WLS) Admin Server URL, username and password have been provided correctly.

The following is the session response for omspatcher:

oracle@emtest13:/patch/25387277$ /u01/app/oracle/middleware/OMSPatcher/omspatcher apply
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation. All rights reserved.

OMSPatcher version : 13.8.0.0.2
OUI version : 13.9.1.0.0
Running from : /u01/app/oracle/middleware
Log file location : /u01/app/oracle/middleware/cfgtoollogs/omspatcher/opatch2017-08-25_19-13-51PM_1.log

OMSPatcher log file: /u01/app/oracle/middleware/cfgtoollogs/omspatcher/25387277/omspatcher_2017-08-25_19-14-53PM_deploy.log

Please enter OMS weblogic admin server URL(t3s://emtest13:7101):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>
Please enter OMS weblogic admin server password:>
Please enter OMS weblogic admin server password:>
Please enter OMS weblogic admin server password:>
Please enter OMS weblogic admin server password:>

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: /u01/app/oracle/middleware/OMSPatcher/omspatcher apply -invPtrLoc /u01/app/oracle/middleware/oraInst.loc OMSPatcher.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: OMSPatcher was not able to find right interview inputs.
OMSPatcher failed:
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: /u01/app/oracle/middleware/OMSPatcher/omspatcher apply -invPtrLoc /u01/app/oracle/middleware/oraInst.loc OMSPatcher.OMS_DISABLE_HOST_CHECK=true)

Please check above conditions and if error(s) still persist, Please contact Oracle support.

Log file location: /u01/app/oracle/middleware/cfgtoollogs/omspatcher/25387277/omspatcher_2017-08-25_19-14-53PM_deploy.log

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

OMSPatcher 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


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