To know about Fast Start Failover in Data Guard
To disable Fast_Start failover apply following command :
DGMGRL> DISABLE FAST_START FAILOVER;
When we perform above command Fast_Start failover is first disabled on target standby database with data guard broker then it is disabled from the primary database. Then these changes are propagated to all standby database present in the data guard broker configuration.
We can disable Fast_Start failover to prevent the observer from initiating a failover. If the Primary database and target standby database of Fast_Start failover does not have connectivity we can use FORCE option.
If this DISABLE FAST_START FAILOVER command is applied on primary database or on bystander standby database then it is disabled locally first then it is recorded in data guard broker metadata then data guard broker propagates these changed to all standby database which is configured in data guard broker configuration and has connectivity to the primary database.
Note: Observer is not stopped when we disable Fast_Start Failover.
Disabling specific condition in Fast_Start Failover :
DISABLE FAST_START FAILOVER CONDITION VALUE;
Example: DISABLE FAST_START FAILOVER “Inaccessible Logfile”
DISABLE FAST_START FAILOVER CONDITION 27102;
Disabling FAST_START failover with FORCE option :
Step 1 :
DGMGRL> show configuration; Configuration - drdb Protection Mode: MaxAvailability Databases: std_testdb - Primary database Error: ORA-16820: fast-start failover observer is no longer observing this database testdb - (*) Physical standby database (disabled) ORA-16661: the standby database needs to be reinstated Fast-Start Failover: ENABLED Configuration Status: ERROR
Step 2: Checking Fast_start failover :
DGMGRL> show fast_start failover; Fast-Start Failover: ENABLED Threshold: 50 seconds Target: testdb Observer: test1.localdomain Lag Limit: 50 seconds (not in use) 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 Offline YES Oracle Error Conditions: (none)
Step 3: I am trying to disable it in a normal way.
DGMGRL> disable fast_start failover; Error: ORA-16652: fast-start failover target standby database is disabled Failed.
We can see here it returns the error.
Step 4: Stopping it with FORCE option.
DGMGRL> disable fast_start failover force; Disabled. DGMGRL>
Stay tuned for More articles on Oracle DataGuard
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Telegram Channel: https://t.me/helporacle
Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/
Joel Perez’s LinkedIn: Joel Perez’s Profile
LinkedIn Group: Oracle Cloud DBAAS
Facebook Page: OracleHelp