Thank you Seth.
Below is details more on how we are doing refresh currently ==>
1. we take backup of Production Primary database.
2. then we get the backup of production database off from ASM to nfs
filesystem which is mounted on both Production and UAT database server so
that we dont have to scp/copy/transfer backups,
3. Then using simple RMAN script we restore production backup to 1st node
of UAT Primary database keeping down UAT standby database.
4. Then after Restore simply recover UAT primary database followed by open
resetlogs.
*5. Main Problem comes here ==> After this open resetlogs when we start
UAT physical standby database it does not recognizes its earlier UAT
Primary database and goes out of sync with its Primary database and as a
result we have to rebuild UAT standby database again.*
*So problem is we have to rebuild UAT standby database again and again i.e
above 5th step after every Production to UAT refresh.*
*I hope i have explained it clearly now*.
Regards
Falgun Patel
On Sat, Nov 9, 2019 at 5:00 AM Seth Miller <sethmiller.sm@xxxxxxxxx> wrote:
Falgun,
Data Guard will recover through a resetlogs so this really comes down to
how you are refreshing your UAT environment. You will need to provide more
details about your refresh process to help you further.
Seth
On Fri, Nov 8, 2019 at 4:40 PM William Beldman <wbeldma@xxxxxx> wrote:
I haven't specifically done what you are asking but I've done some
similar
things in the past so I wanted to do a little more reading on the subject.
According to the documentation, DUPLICATE automatically executes a
RESETLOGS:
https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/DUPLICATE.html#GUID-E13D8A02-80F9-49A2-9C31-92DD3A795CE4
which is what changes the incarnation number:
https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/managing-oracle-data-guard-physical-standby-databases.html#GUID-02218512-31A6-461E-96B4-0B9997DCFC4A
It sounds like stopping apply on the standby and turning it back on after
the
DUPLICATE should work. Alternatively, you could use DUPLICATE ... NOOPEN
and
then delay the RESETLOGS.
I'd also be interested in what others are doing.
On Saturday November 9 2019 03:35:22 AM falgun patel wrote:
I have question related to Dataguard.Database
I get 2 to 4 times request in a month to refresh Oracle Production
to UAT Database.UAT
Production and UAT both databases are on 11g R2 version.
Production Database Setup is 4 Node RAC i.e. 2 Node Primary and 2 Node
Physical Standby.
UAT Database Setup is 4 Node RAC i.e. 2 Node Primary and 2 Node Physical
Standby.
My Question:
Every time if refresh Production database to UAT , and since every time
incarnation gets changed in UAT after refresh from production database.
Due to this my current UAT Physical standby database is of no use as it
goes out of sync.
Everytime After this production to UAT DB refresh i have to rebuild my
physical standby database again and again.
I want to know if there is any way i can avoid this rebuild physical
standby database after every UAT database refresh ?
Please provide me detailed steps.
