Description:-
- If the primary and target standby database have a network connection, use DISABLE FAST_START FAILOVER without the FORCE option to disable fast-start failover on all databases in the broker configuration.
- If errors occur during the disable operation, the broker returns an error message and stops the disable operation.
- You may need to reissue the DISABLE FAST_START FAILOVER command with the FORCE option to override the error conditions and disable fast-start failover on the database to which you are connected.
- Use DISABLE FAST_START FAILOVER with the FORCE option when the network between the primary and target standby databases is disconnected or when the database upon which the command is received does not have a connection with the primary database.
- The FORCE option disables fast-start failover on the database to which you are connected, even when errors occur.
- Disabling fast-start failover with the FORCE option on a primary database that is disconnected from the observer and the target standby database does not prevent the observer from initiating a fast-start failover to the target standby database.
Let’s start the demo:-
Step:-1 Show configuration
DGMGRL> connect sys/oracle@chennai
Connected to “CHENNAI”
Connected as SYSDBA.
DGMGRL> show configuration;
Configuration – hari
Protection Mode: MaxAvailability
Members:
delhi – Primary database
chennai – (*) Physical standby database
Fast-Start Failover: Enabled in Zero Data Loss Mode
Configuration Status:
SUCCESS (status updated 60 seconds ago)
Step:-2 Disable Fast start Failover
DGMGRL> DISABLE FAST_START FAILOVER;
Disabled.
DGMGRL> show configuration;
Configuration – hari
Protection Mode: MaxAvailability
Members:
delhi – Primary database
chennai – Physical standby database
Fast-Start Failover: Disabled
Configuration Status:
SUCCESS (status updated 54 seconds ago)
Step3:-Check the Health Contention of fast_start failover
DGMGRL> SHOW FAST_START FAILOVER
Fast-Start Failover: Disabled
Protection Mode: MaxAvailability
Lag Limit: 0 seconds
Threshold: 30 seconds
Active Target: (none)
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