EM 12c: Opatchauto Fails when WLS Administration Server is Secured With Custom Java Keystore (Doc ID 2079881.1)

Last updated on MAY 15, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.3.0 to 12.1.0.5.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Attempting to apply any patch to 12.1.0.3 or above version OMS using opatchauto fails with the below error:

$opatchauto apply -property_file /cloud/swlib/oracle/oms_patches/propertyfile OPatchAuto.OMS_DISABLE_HOST_CHECK=true
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation. All rights reserved.

OPatchauto version : 11.1.0.12.3
OUI version : 11.1.0.12.0
Running from : /u01/app/oracle/MW12104/oms
Log file location : <OMS_HOME>/cfgtoollogs/opatch/opatch2015-10-27_08-27-23AM_1.log

OPatchauto log file: <OMS_HOME>/cfgtoollogs/opatchauto/21302024/opatch_oms_2015-10-27_08-27-24AM_deploy.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 -property_file /cloud/swlib/oracle/oms_patches/propertyfile OPatchAuto.OMS_DISABLE_HOST_CHECK=true -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 -property_file /cloud/swlib/oracle/oms_patches/propertyfile OPatchAuto.OMS_DISABLE_HOST_CHECK=true -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: <OMS_HOME>/cfgtoollogs/opatchauto/21302024/opatch_oms_2015-10-27_08-27-24AM_deploy.log

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

OPatchauto failed with error code 231

Values provided for the WLS console are valid and it is possible to login to the WLS console URL using these details.

Changes

The Weblogic components were recently secured with a java keystore containing custom certificate, following the steps in
<Note 1527874.1> - EM 12c: Steps to Create and Import Third Party / Self-Signed SSL Certificates for WebLogic Server in an Enterprise Manager 12c Cloud Control Installation

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms