Description:-
- The fast-start failover target standby database can be changed dynamically, to another standby database in the target list, without disabling fast-start failover.
- In earlier releases of Oracle Database, you had to disable fast-start failover to move to a new target standby database. This exposes the broker configuration to a period where automatic failover cannot be used at all. You use the SET FAST_START FAILOVER TARGET command to dynamically change the fast-start failover target standby database.
Example:- If we have two standby database we can decide to failover target database .Without disabling fast_start Failover.
DGMGRL> ENABLE FAST_START FAILOVER OBSERVE ONLY;
Enabled in Observe-Only Mode.
DGMGRL> SET FAST_START FAILOVER TARGET TO ‘chennai’
Waiting for Fast-Start Failover target to change to “chennai”…
Succeeded.
DGMGRL> SHOW FAST_START FAILOVER;
Fast-Start Failover: Enabled in Observe-Only Mode
Protection Mode: MaxAvailability
Lag Limit: 0 seconds
Threshold: 30 seconds
Active Target: chennai
Potential Targets: “chennai”
chennai valid
Observer: dev19c
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Observer Reconnect: (none)
Observer Override: FALSE
Configurable Failover Conditions
Health Conditions:
Corrupted Controlfile YES
Corrupted Dictionary YES
Inaccessible Logfile NO
Stuck Archiver NO
Datafile Write Errors YES
Oracle Error Conditions:
(none)
Connect with me:-
Telegram App:https://t.me/oracledbwr
LinkedIn:https://www.linkedin.com/in/hariprasathdba
Facebook:https://www.facebook.com/HariPrasathdba
FB Group:https://www.facebook.com/groups/894402327369506/
FB Page : https://www.facebook.com/dbahariprasath/?
Twitter : https://twitter.com/hariprasathdba
