After Installing 10.1.3 in Cold Failover Cluster OPMN Does Not Start and AS Console is Inaccessible
Last updated on JUNE 22, 2017
Applies to:Oracle Fusion Middleware - Version 10.1.3.0.0 to 10.1.3.1.0 [Release AS10gR3]
Information in this document applies to any platform.
The objective is to install an OracleAS 10g Release 3 (10.1.3.x) in active passive mode on a Cold Failover Cluster.
The two OracleAS nodes in the cluster have been installed successfully - the installer reported no errors
Post- install it is apparent there is a problem with OPMN
Issuing 'opmnctl startall' appears to work - it returns no errors.
Issuing 'opmnctl status' returns the error, "Unable to connect to opmn", similar to the following error stack:
Unable to connect to opmn.
Opmn may not be up.
The opmn.log contains the lines
... [libopmnoc4j] Pinging failed for proc: 1810172380 because no notifications have been received from the process yet
... [libopmnoc4j] Process Ping Failed: default_group~Home~default_group~1 (1810172380:4028)
... [pm-requests] Request 6 Started. Command: /restart?process-type=HTTP_Server
... [pm-process] Restarting Process: HTTP_Server~HTTP_Server~HTTP_Server~1 (1810172379:1952)
... [pm-process] Process Alive: HTTP_Server~HTTP_Server~HTTP_Server~1 (1810172379:1952)
... [pm-requests] Request 6 Completed. Command: /restart?process-type=HTTP_Server
... [ons-secure] Connection 188.8.131.524,6200 SSL handshake failed
... [ons-messages] Connection 127.0.0.1,6100 socket data stream is out of sync
... [ons-connect] Passive connection 127.0.0.1,6100 missing connect
The AS Console is also inaccessible. On entering the AS Console the browser returns a blank page
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