PCP Concurrent Manager Failover/Failback Does Not Work When Application Listener is Down On Primary Node
(Doc ID 1389261.1)
Last updated on APRIL 07, 2022
Applies to:
Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]Information in this document applies to any platform.
Symptoms
When the primary node becomes available (after a crash / reboot), the Internal Concurrent Manager (ICM) will try to failover to the primary node from the running node and fails with the error below. It happens when primary node is just pingable and application listener is down.
Starting Internal Concurrent Manager Concurrent Manager : 05-MAR-2011 10:39:03
CONC-SM TNS FAIL
: ICM failed to start for target <target_node_name>. Review ICM log files for additional information.
Process monitor session ended : 05-MAR-2011 10:39:03
CONC-SM TNS FAIL
: ICM failed to start for target <target_node_name>. Review ICM log files for additional information.
Process monitor session ended : 05-MAR-2011 10:39:03
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 |
| References |