I have an Active DataGuard, Oracle version 22.214.171.124 and Solaris 10.
I have to do a test on the Active DataGuard environment, I want to open this database to run multiple scripts DML. At the end I must return to the DataGuard active as it was before the opening to continue with normal operation.
I appreciate the document indicate commands or procedure I should run to do this activity.
SQL> SELECT database_role, open_mode FROM v$database;
SQL> alter database recover managed standby database cancel;
SQL> alter database open;
SQL> alter database recover managed standby database disconnect from session;
SQL> select process,status,sequence# from v$managed_standby;
If you have Data Guard Broker setup then
DGMGRL > edit database physt set state=apply-off;
SYS@physt > alter database open read only;
DGMGRL > edit database physt set state=apply-on;
Edited by: mseberg on Oct 3, 2012 3:12 PM
Milton, you understand Active Data Guard make the Standby Database a "Reader" database. It allows read-only access on the standby at the same time as archiving transactions from the primary.
So your inserts need to be on the primary.
When I created this adg enviroment, I read a note indicating that he could open the database for testing and then return to the point before the opening to continue the active DataGuard. I want to do this test and do not remember the number of document information and commands.
Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02
See - 9.2 Opening a Physical Standby Database
As i understand you want to open the standby database in read/write mode test it and again revert back to standby by database. If it is so then following link might help you.
Active Data Guard resp. Real-Time Query will never allow for DML on the Standby DB. Period.
You can open a Physical Standby Read-Write and do DML then, but it will no longer show the same state as the Primary. In other words: Real-Time Query is off then.
One convenient way to have a Physical Standby opened Read-Write, do anything and then reconvert it into Physical Standby is a Snapshot Standby Database.
There is no (direct) relation to Active Data Guard here, though.
"Don't believe it, test it!"