Primary DB: 22.214.171.124 Enterprise
Standby DB: 126.96.36.199 Enterprise
I've found several articles on making changes on a Physical Standby DB, but I've been having difficulty locating how to enable user testing on a Transient Logical Standby DB (then flashing back their changes and re-enabling log transport and SQL Apply after the testing has been completed).
Based on what I know of Logical Standby Databases, I wrote up the following procedures. However, this is untested since if I botch up the Standby DB, I can't simply re-duplicate the DB through RMAN since the database versions are different. I'll essentially have to re-clone the Primary DB, reconfigure the Standby for dataguard, upgrade the Standby DB version, etc, etc... basically, a lot of work that I would prefer to avoid, if possible...
If someone who has had experience with this can look over my below procedures and let me know if i'm forgetting anything, or what potential issues/caveats I should watch out for or be aware of, I would greatly appreciate it:
*note: the primary => standby log transport is specified in log_archive_dest_3
PRIMARY alter system set log_archive_dest_state_3=defer scope=both; STANDBY alter database stop logical standby apply; alter database guard none; alter database flashback on; create restore point before_testing guarantee flashback database; *AFTER TESTING IS DONE* STANDBY flashback database to restore point 'before_testing'; drop restore point before_testing; alter database flashback off; alter database guard all; alter database start logical standby apply immediate; PRIMARY alter system set log_archive_dest_state_3=enable scope=both;