My Oracle Support Banner

Fast-Start Failover May Fail if Primary Nodes Crash One After Another (Doc ID 1995640.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Oracle Database Exadata 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


If all instances of a primary crash and there is any delay in when each instance goes down with respect to the other instances, a Data Guard environment configured for MAXIMUM AVAILABILITY mode can become UNSYNCHRONIZED.

For example, let's say with a 2-node RAC primary, instance #1 goes down at 11:23:48.  Then at 11:24:20, instance #2 crashes. This would result in standby becoming unsynchronized.


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.