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 









Data Guard Log Management Tips

Oracle Database Tips by Donald BurlesonDecember 9, 2015

Oracle Data GuardChapter 6 - Switchover and Failover

Role Transition Using Failover

After the failover, the original primary database is removed from the Data Guard configuration. Other standby databases may or may not be affected depending on the type of failover. Based on the amount of data loss and the impact on other standby databases in the Data Guard configuration, the failover operation can be classified into two categories.

Graceful Failover

A graceful failover is similar to a switchover operation except that in a graceful failover the original primary database is discarded. Graceful failover reduces the amount of data loss and the impact on other standby databases. A graceful failover is ideally suited for physical standby databases, in which standby redo logs can be created and maintained. Graceful failover supports the recovery of all possible redo data from the standby redo log file or the archived redo log file before switching the standby database over to the primary database.

Depending on the type of protection mode, failover can occur with no data loss or minimal data loss. In some cases, even if the primary database is running in maximum protection mode, it may not be possible to recover all the redo data from the standby redo log file. One such situation is a corrupt standby redo log file during the disaster of the primary database.  Fortunately, the probability of these two events occurring simultaneously is negligible. Details of graceful failover will be presented later in this chapter.

Forced Failover

A forced failover operation can result in data loss. However, the amount of data loss can be minimized by copying the online log files and the archived redo log files from the original primary database and registering with the standby database. As a result, the amount of data that can be saved depends on the kind of failure on the primary database.

The above text is an excerpt from the book: Oracle Data Guard Handbook

Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


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.