After Fail Over to the Second Node of OracleAS Cold Failover Cluster OPMN Fails to Start
(Doc ID 420389.1)
Last updated on JUNE 01, 2023
Applies to:
Oracle Fusion Middleware - Version 9.0.2.0.1 to 10.1.2.0.2 [Release 9iAS to AS10gR2]Information in this document applies to any platform.
Symptoms
This note addresses the following High Availability (HA) setup:
- Collocated Infrastructure (Metadata Repository plus Identity Management in a single oracle home) is installed in active-passive mode onto the shared disk of a Cold Failover Cluster (CFC).
- Each node of the CFC has an installation of OracleAS Middle Tier on a local disk.
When the AS Infrastructure is failed over to Node 1, everything works fine.
When the AS Infrastructure is failed over to Node 2 it is not possible to start the opmn daemon, and therefore any of the opmn-managed processes in one of the oracle homes on Node 2.
The following error is reported to the command line:
Communication error with the OPMN server local port.
Check the OPMN log files
The requirement is to be able to fail over the AS Infrastructure to either node of the CFC and start all of the opmn-managed components in both the Infrastructure and Middle Tier homes.
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 |