My Oracle Support Banner

Data Guard RAC How do you avoid a false fast start failover to the physical standby when a RAC node fails (Doc ID 1319917.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


The Environment:

Multiple Node RAC Primary
Multiple Node RAC Physical Standby
Fast Start Failover is configured and the observer is running.
The Problem:
When one of the RAC nodes fails in the Primary Site the observer triggers a false faststart failover to the Standby site even though there are nodes and RAC instances still available at the Primary site. 
This is considered to be a false fail over.  If the environment is configured correctly a fail over to the standby site should not occur given this specific scenario.  The Observer should be reconnecting to the remaining Primary Site instances and a fail over only initiated when the Observer and the Standby site are no longer able to connect to any of the RAC primary site instances.  All primary site instances must be unavailable before a fail over occurs.


The Fast Start Failover threshold is set to the default value of 30 seconds or less.  This will be to small for RAC configurations.


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

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