Re: is there any way i can avoid rebuild physical standby database after every PROD to UAT database refresh ?

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.
>
>
>
> I get 2 to 4 times request in a month to refresh Oracle Production Database
> to UAT Database.
>
>
>
> 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 UAT
> 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.

--
http://www.freelists.org/webpage/oracle-l