Both options are valid for 11G and later. Just keep in mind that they require Enterprise Edition version.

“A snapshot standby database is a fully update-able standby database that is created by converting a physical standby database into a snapshot standby database.

A snapshot Standby is open in the read-write mode and hence it is possible to process transactions independently of the primary database. At the same time, it maintains protection by continuing to receive data from the production database, archiving it for later use.

Using a single command changes made while read-write mode can be discarded and quickly resynchronize the standby with the primary database.” Met.note [ID 443720.1]

I haven’t tested the snapshot standby. Will do and consider creating a blog about it.

In 11.1 and later you can use the snapshot standby to achieve the same without knowing about the details.

It has the added advantage that additional standby databases don’t start receiving archived logs from the newly activated standby.

Cheers,

Martin

Great Work and excellent presentation to utilize the feature which otherwise people like me don’t realize it

1. Flashback to the restore point:

SQL> STARTUP MOUNT FORCE;
SQL> FLASHBACK DATABASE TO RESTORE POINT TEST_NEW_FEATURE;
SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
SQL> ALTER SYSTEM SET DG_BROKER_START=TRUE;
SQL> STARTUP MOUNT FORCE;
SQL> DROP RESTORE POINT TEST_NEW_FEATURE;

SQL> DROP RESTORE POINT TEST_NEW_FEATURE;

Restore point dropped.