My Oracle Support Banner

Automatic failover doesn't happen when primary host become unreachable (Doc ID 2764055.1)

Last updated on APRIL 02, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 19.9.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Primary Host unreachable.

Observer detect outage and never proceed with automatic failover

below errors are observed:-

Attempting Fast-Start Failover because the threshold of 30 seconds has elapsed.
2021-02-06T01:02:11.628278+03:00
DMON: Killing process NSV0 (PID=27409)
2021-02-06T01:02:27.388586+03:00
Attempting Fast-Start Failover because the threshold of 30 seconds has elapsed.
2021-02-06T01:02:44.758333+03:00
Attempting Fast-Start Failover because the threshold of 30 seconds has elapsed.
2021-02-06T01:03:01.852890+03:00
Attempting Fast-Start Failover because the threshold of 30 seconds has elapsed.
2021-02-06T01:03:10.219258+03:00
Fore: NSV0 did not stop within 60 seconds, killing it now

Once The primary become reachable by restarting it, failover is done

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


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