RE: Cloning from physical standby

From: Amaral, Rui <>
Date: Mon, 31 Jan 2011 08:41:40 -0500
Message-ID: <1B861F1ABE40A84AA92AD585B20C558B26F0989A35_at_EX7T2-CV06.TDBFG.COM>

I agree with that as well. I did the same as you suggested and what Michael re-iterated (using HP's business copy). Also used the rman processs as well. It sounds about right.

From: [] On Behalf Of Michael Brown Sent: Monday, January 31, 2011 8:36 AM
Cc:; Subject: Re: Cloning from physical standby

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

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" <<>> 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
NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to for instructions. AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au pour des instructions. --
Received on Mon Jan 31 2011 - 07:41:40 CST

Original text of this message