[Translated from mos] the flashback primary database method in the dg Environment,
Flashback primary database method in the dg Environment
The intention of this article is: the flashback standby database method after flashback has primary database.
Reference:
How To Flashback Primary Database In Standby Configuration (Document ID 728374.1)
Applicable:
Oracle Database-Enterprise Edition-Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Information in this document applies to any platform.
Solution:
1. Shutdown primary database .SQL> SHUTDOWN IMMEDIATE2. Start primary database in mount stageSQL> STARTUP MOUNT3. Flashback primary database to specified scnSQL> FLASHBACK DATABASE TO SCN <scn_number>;4. Open primary database with reset logs.SQL> ALTER DATABASE OPEN RESETLOGS;5. Cancel media recovery on the standby database (if not already done).SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;6. Check current_scn on the standby database, If flashback scn is greater then current_scn then skip next step (step 7).SQL> SELECT CURRENT_SCN FROM V$DATABASE;7. Flashback Standby databaseSQL> FLASHBACK STANDBY DATABASE TO SCN <scn_number -2>; (on standby database)8. Start managed recovery on the standby databaseSQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;Due to Bug 7516849 and Bug 6967591 Media recovery on physical standby may not work properly after the flashback. In order to avoid these bugs, please recreate the Standby Controlfile using these Notes:Note 459411.1 : Steps to recreate a Physical Standby Controlfile OR Note 734862.1 : Step by step guide on how to recreate standby control file when datafiles are on ASM and using Oracle Managed Files