Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







fast-start failover tips

Oracle Tips by Burleson

December 12, 2011 - Updated March 5, 2016

Question:  I want to deploy fast_start failover, but I don't understand the steps for enabling fast_start failover and verifying that fast_start failover is working?  Can you help?

Answer:  (By Rampant aauthor Laurent Schneider:)  Prerequisites for fast_start failover include:

  • Enable fast_start failover you must have a working set of primary / standby databases.
  • Both databases must be in flashback mode.
  • Verify your Data Guard configuration with OEM.  You will need to review your Data Guard property.

lsc01 my primary, lsc05 my standby

edit database lsc01 set LogXptMode='SYNC';

edit database lsc01 set FastStartFailoverTarget= 'lsc05'

edit database lsc05 set LogXptMode='SYNC';

edit database lsc05 set FastStartFailoverTarget= 'lsc01'


Next, you need to start the fast_start failover observer  (using the Data Guard dgmgrl -silent "start observer" command.  You submit this dgmgrl command in the background with the nohup command so it is always running as a daemon process.:

nohup dgmgrl -silent sys/*** "start observer" &

note: it does not work if you connect with /. You will get DGM-16979 if you use / or if you use different passwords in standby and primary.

Now that we have the fast_start failover prerequisites, enable fast_start failover in dgmgrl:

DGMGRL> enable fast_start failover

Before you switch, check the listener.ora is correctly configured :



    (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521))

The GLOBAL_DBNAME is mandatory to enable a painless switchover. Otherwise the standby startup will fail with ORA-12514.


Alternatively in 11gR2 and beyond, you can set the Data Guard property StaticConnectIdentifier to use a SID instead of   service name :

edit database lsc05 set property StaticConnectIdentifier=

edit database lsc01 set property StaticConnectIdentifier=

In this case you will not need global_dbname in listener.ora. (See MOSC note 308943.1)

OK, let's see how fast I can switch

$ time dgmgrl -silent sys/*** "switchover to lsc05"

Performing switchover NOW, please wait...

New primary database "lsc05" is opening...

Operation requires shutdown of instance "LSC01" on database "lsc01"

Shutting down instance "LSC01"...

ORACLE instance shut down.

Operation requires startup of instance "LSC01" on database "lsc01"

Starting instance "LSC01"...

ORACLE instance started.

Database mounted.

Switchover succeeded, new primary is "lsc05"

real    1m10.685s

user    0m0.052s

sys     0m0.109s

About one minute. most of the time was spent restarting the original primary as a standby, the primary was already available for queries after about 20 seconds.

Get the Complete
Oracle SQL Tuning Information 

The landmark book "Advanced Oracle SQL Tuning  The Definitive Reference"  is filled with valuable information on Oracle SQL Tuning. This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.



Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster