My Oracle Support Banner

Broker does Not failover to the Second target configured in FastStartFailoverTarget (Doc ID 2878478.1)

Last updated on JUNE 28, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 to 21.6 [Release 12.2 to 21.0]
Information in this document applies to any platform.

Symptoms

From 12.2 it is possible to configure multiple Fast-Start Failover Targets

But Broker was Not switching to  Second FSFO Target when the First Target is Not reachable

Doc : https://docs.oracle.com/en/database/oracle/oracle-database/19/dgbkr/using-data-guard-broker-to-manage-switchovers-failovers.html#GUID-995CED84-BEA1-4675-9C68-B37CB996924F

5.5 Fast-Start Failover

If the primary database has multiple standby databases, then you can specify multiple fast-start failover targets, using the FastStartFailoverTarget property.
The targets are referred to as candidate targets. The broker selects a target based on the order in which they are specified on the FaststartFailoverTarget property.
If the designated fast-start failover target develops a problem and cannot be the target of a failover, then the broker automatically changes the fast-start failover target to one of the other candidate targets.

 

 

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
Cause
Solution


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