Re: Cloning from physical standby

From: Michael Brown <dba_at_michael-brown.org>
Date: Mon, 31 Jan 2011 08:36:01 -0500
Message-Id: <2CAC844B-0F05-4E43-8B80-7F3067D820D8_at_michael-brown.org>

You are not creating new controlfiles for the standby, so you do not want to activate it.

What you are asking about is exactly how I used to do clones in an 8.1.7 and then 9.2 environment.

I agree with the suggestion that rman duplicate may be the easier way to go today although a piece of this is how you will copy. If you are on a SAN that supports read/write snapshots and you are cloning often, shutting down the standby long enough to get a fresh snapshot is a very easy way to clone (be aware of how your snapshots work when data changes on both the source and target or you can be shocked at the space required).

--
Michael Brown
dba_at_michael-brown.org
http://blog.michael-brown.org




On Jan 31, 2011, at 6:37 AM, Harel Safra wrote:



> Sounds good.

> I'd activate the standby (failover) instead of recreating the controlfile

> 

> On Jan 31, 2011 1:23 PM, "David Pintor" <painterman_at_gmail.com> wrote:

> > Hi,

> > 

> > 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.

> > 

> > David



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

Received on Mon Jan 31 2011 - 07:36:01 CST