How to Perform Oracle Instance Registration via a Secure Port With OPMNCTL (Doc ID 1356248.1)

Last updated on JULY 03, 2023

Applies to:

Goal

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
...

Solution

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