My Oracle Support Banner

11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus (Doc ID 1304939.1)

Last updated on JANUARY 08, 2024

Applies to:

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


Perform trouble free Data Guard switchover.

Note: for Data Guard switchover using the Broker please refer to Note 1305019.1 - "11.2 Data Guard Physical Standby Switchover Best Practices using the Broker"


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
 I. Prerequisites / Preparation
 Apply Latest Patch Bundle.
 Review Primary Database Initialization Parameters
 Verify the Setup
 Understand and Test Fallback Options
 II. Pre-Switchover Checks
 Verify Managed Recovery is running on the standby
 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 Alert Logs (optional) on all instances
 Create Guaranteed Restore Points (optional)
 Verify that the primary database can be switched to the standby role
 If The Primary is a RAC, then shutdown all secondary primary instances
 Switchover the primary to a standby database
 Verify the standby has received the end-of-redo (EOR) log(s)
 Verify that the standby database can be switched to the primary role
 Switchover the standby database to a primary
 Open the new primary database
 Correct any tempfile mismatch
 Restart the new standby
 Contingency or Fallback
 IV. Post-Switchover Steps
 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.