RE: Cloning from physical standby

  • From: "Sheehan, Jeremy" <JEREMY.SHEEHAN@xxxxxxxxxxxxxxxxx>
  • To: "painterman@xxxxxxxxx" <painterman@xxxxxxxxx>, Subodh Deshpande <deshpande.subodh@xxxxxxxxx>
  • Date: Mon, 31 Jan 2011 09:17:44 -0500

Be mindful of anything set to nologging the database as well.  We had some 
issues with materialized views set to nologging when we cloned from a standby.


From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of David Pintor
Sent: Monday, January 31, 2011 9:07 AM
To: Subodh Deshpande
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Cloning from physical standby

Will do, Sobodh, and thanks to everyone who commented.

I think I'm not going to use RMAN cause i'm not really familiar with the syntax 
and need to start this right now, but i reckon it might be easier to do!



On 31 January 2011 14:03, Subodh Deshpande 
<deshpande.subodh@xxxxxxxxx<mailto:deshpande.subodh@xxxxxxxxx>> wrote:
just update when you are completed, I am bit curious...:)..subodh

On 31 January 2011 16:52, David Pintor 
<painterman@xxxxxxxxx<mailto:painterman@xxxxxxxxx>> wrote:

This question might seem a bit obvious for many of you, I'm just trying to 
figure out which would be the best way to clone a database using the physical 
standby (so i don't need to touch prod) into a test environment. I was thinking 
about the following steps:

- Stopping the physical standby
- Copying the files across to the test environment
- Restarting the physical standby (so it gets in sync again)
- Recreating the control file in test and starting up the db.

Would this, roughly, be correct?

Thanks for your help.



Other related posts: