In PCP/RAC Environment CM Failover Takes Long Time
Last updated on JULY 12, 2016
Applies to:Oracle Application Object Library - Version 22.214.171.124 to 126.96.36.199 [Release 11.5]
Information in this document applies to any platform.
This problem can occur on any platform.
In a PCP/RAC environment when one concurrent node fails, failover to surviving
node takes 30-35 minutes. The database sessions associated with the managers, on the node which is failed, take 30 minutes to exit.
Even with sqlnet.expire_time in sqlnet.ora is set to 1, it takes 30-35 minutes for DCD (Dead Connection Detection) to clean up the sessions from the failed node.
The following steps were attempted, but did not help
On the database nodes, for the database listeners (not apps listener) set sqlnet.expire_time = 1
On Concurrent manager nodes, set the following env variable before starting the managers:
Linux, tune the kernel as follows (other platforms, Please find the analogous tcp/ip parameters and tune them)
On the database nodes AND the Concurrent nodes:
tcp_keepalive_intvl = 45
tcp_keepalive_probes = 4
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