How To Failover and Flashback a Physical Standby for testing without recreating broker configuration and database
(Doc ID 2060572.1)
Last updated on OCTOBER 18, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
For testing purpose it may be needed to execute a failover to a physical standby in a data guard environment.
This may be required, for example, to test the disaster recovery procedure so it should be as similar as possible to a real situation.
After failover via dg broker the standby database, promoted to a read write primary, will be used to test applications.
After all the testing, the activated standby should be recreated from the "real" primary.
Since it may be time consuming and some work may be avoided, these steps may be used to recreate the DR enviroment.
It's fundamental that primary and standby site are isolated during test.
For a similar scenario without dg broker note 805438.1 may be used.
To make connections work between your on-prem and Exadata cloud, you "might" need to open firewall
rules from your internal as well as from cloud side using self service firewalls.
Enabling Network Access to a Compute Node
There are also two alternative ways to test a failover:
The reinstate option to convert the old primary to standby and in case switch back roles
Add an additional Physical Standby Database for Failover Tests to ensure DR at any Time
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