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

From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Sun, 10 Nov 2019 10:28:53 -0500
Message-ID: <089f01d597db$8fa45040$aeecf0c0$_at_rsiz.com>



What exactly do you wish to refresh from production?  

Can you accomplish your goal with transportable tablespaces and the files that contain them?  

There is probably a difference in approach with the not necessarily equal efforts of goals for “least human intervention” versus least physical activity on the servers.  

Increasing complexity is usually proportional to increasing failure rates, although different folks put different metrics on discrete human actions, number of steps, and underlying complexity.  

And at some scale versus any then current variety of physical components, reasonable time to complete and consumption of resource limited resources may require additional complexity to complete in time and resource consumption that is acceptable.  

I personally have a distaste for the physical machinery wasting cycles, but that is something I dismiss depending on the real world situation.  

So is avoiding the rebuilds a matter of taste or a real issue of time to complete?  

Clearly stating the goal (including the acceptable service levels and physical resource capacities) is a useful starting point.  

The short answer to your question is “yes,” but a presumed toolset and exactly what you mean by a physical standby database may limit your options.  

Good luck,  

mwf  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Franck Pachot Sent: Saturday, November 09, 2019 4:31 PM To: Mladen Gogala
Cc: Oracle-L Freelists
Subject: Re: is there any way i can avoid rebuild physical standby database after every PROD to UAT database refresh ?  

Hi Falgun,

Even without resetlogs, you have to rebuild the standby because the primary has been overwritten.

If you do not open resetlogs (like with a restore without open) then you can rebuild the standby from the same backups that were used for the primary. But I'm not sure that it will be better than re-creating the standby from the primary. Is that a problem if it is automated (duplicate for standby, or restore from service is easily automated).

Regards,

Franck.  

On Sat, Nov 9, 2019 at 1:16 AM Mladen Gogala <gogala.mladen_at_gmail.com> wrote:  

On 11/8/19 5:05 PM, 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.

--

Regards

Falgun Patel

Hi Falgun,
Of course you can avoid the rebuild of physical standby database. Why are changing the incarnation? Let me guess: you are connecting to catalog. I have been refreshing databases in the ancient times of 9.2 without changing the incarnation. You don't connect to catalog and you don't register the newly minted UAT copy to catalog. Also, use SRDF or whatever tool your array offers. Regards      

--

Mladen Gogala
Database Consultant
Tel: (347) 321-1217

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Nov 10 2019 - 16:28:53 CET

Original text of this message