How to Perform Oracle Instance Registration via a Secure Port With OPMNCTL
(Doc ID 1356248.1)
Last updated on JULY 15, 2020
Applies to:Oracle Fusion Middleware - Version 188.8.131.52.0 to 184.108.40.206.0 [Release Oracle11g]
Information in this document applies to any platform.
If the WebLogic AdminServer has been configured to use HTTPS only as per "<Note 1353951.1> How to Configure WebLogic Admin Server to Listen on SSL Only and associated FMW Considerations", then it is only possible to connect to the AdminServer HTTPS port when performing opmnctl commands, that access the Admin Server. For example "opmnctl registerinstance". This document explains what steps are required to perform this instance registration via a secure port with the OPMNCTL utility.
The instructions in this document may be needed if you are getting the following errors:
Command failed: Unable to connect to the admin server. Verify it has been started and is accessible.
Details are logged in <ORACLE_INSTANCE>/diagnostics/logs/OPMN/opmn/provision.log
And the provision.log shows:
SEVERE: Command failed:
oracle.as.config.ProvisionException: Unable to connect to the admin server. Verify it has been started and is accessible.
Caused by: java.io.IOException: Unable to connect to the server. Verify it has been started and is accessible.
Caused by: java.io.IOException: Couldn't connect to the specified host
Caused by: javax.naming.NamingException: Couldn't connect to the specified host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
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