Here I am simulating scenario for fast-start failover.

Configuring Fast-Start Fail Over

Step 1: View fast_start failover is enabled or not.

Step 2: I am aborting the Simulating and Restriction After enabling FAST_START failoverdatabase.

Step 3: Check observer

Step 4: Now again I am starting a primary database.

Step 5: check observer status

Step 6: Check alert log file

Step 7: check the newly converted primary database.

Step 8: Open a standby database.

Step 9: Check status

Step 10: check the reason for failover

Restrictions after Enabling FAST_START failover :
We have seen an overview of Fast_start failover in the previous article. In this article, we will see restrictions or we can say operations that are prohibited in data guard environment after enabling FAST_START failover.
  1. We can not change Protection Mode once Fast_Start failover is enabled.
  2. We cannot change the LogXptMode property for Primary or Standby database.
  3. We can not perform failover o4xfrjb7r switchover to standby database that not target database for fast-start failover.
  4. We can not disable or delete  data guard broker configuration, trying to do so will result in the following error :

5. We can not disable or remover standby database that is a target or fast_start failover.

6. We can not change FastStartFailoverTarget property once fast_start failover is enabled.
7. Failover to an unsynchronized fast-start failover target is prohibited.

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:

Skant Gupta’s LinkedIn:

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.