12c Data guard Switchover Best Practices using SQLPLUS (Doc ID 1578787.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.

Goal

* Reviewed for Relevance 16-Jul-2015 *

This Document describes step by step method to perform switchover on Physical Standby Environment using SQLPLUS.

Solution

	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

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

This Document describes step by step method to perform switchover on Physical Standby Environment using SQLPLUS.

I. Pre-Switchover check

Verify that the target standby is ready for switchover.

Checks ORL status on target standby.

What to do?

Verify Primary and Standby tempfiles match

NOTE : For multiple Standby environment make sure all the standby in SYNC with primary.

Check if log_archive_Dest(remote redo transport) set on Standby side

If switchover_status(v$database) shows UNRESOLVABLE GAP in RAC/non RAC environment

II SWITCHOVER

Enable tracing on both primary and standby to diagnose in case of any issue.

Tail Alert Logs (optional) on all instances

Switchover the standby database to a primary

Open the new primary database

Restart the new standby

III. Post - Switchover Check

Set Trace to Prior Value

Verify that the new primary shipping logs to standby and standby is applying.

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