My Oracle Support Banner

11.2 Data Guard Physical Standby Switchover Best Practices using the Broker (Doc ID 1305019.1)

Last updated on AUGUST 23, 2023

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


*** Reviewed for Relevance 16-Jul-2015 ***

Perform trouble free Data Guard Switchover.

Note: for Data Guard switchover using SQL*Plus please refer to
Note 1304939.1 - "11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus"


Would you like to explore this Topic further with other Oracle Customers, Oracle Employees and Industry Experts ??

You can discuss this Note, show your Experiences or ask Questions about it directly right at the Bottom of this Note in the Discussion Thread about this Document.

If you want to discover Discussions about other Articles and Subjects or even post new Discussions you can access the My Oracle Support Community Page for High Availability Data Guard



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Location:  /oradata/order_db/redo/
Wallet Location: /u01/app/oracle/admin/
 I. Prerequisites/Preparation
 Apply Latest Patch Bundle
 Verify the Setup
 Understand and Test Fallback Options

Appendix A.4 Problems Switching Over to a Physical Standby Database
 II. Pre-Switchover Checks
 Verify Configuration Health
 Verify Sufficient Number of Archiver Processes
 Ensure Online Redo Log Files on the Target Physical Standby have been cleared
 Verify there are no large Gaps
 Verify Primary and Standby tempfiles match and all datafiles are ONLINE
 III. Switchover
 Cancel any apply delay for the target standby
 Clear Potential Blocking Parameters & Jobs
 Shutdown all mid-tiers (optional)
 Turn on Data Guard tracing on primary and standby
 Tail Broker and Alert Logs (optional) on all instances
 Create Guaranteed Restore Points (optional)
 Perform the Switchover
 Contingency or Fallback
 IV. Post-Switchover Steps
 Reset apply delay for the target standby
 Set Trace to Prior Value
 Reset Jobs
 Drop any Switchover Guaranteed Restore Points

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.