Re: Duplicating from copy of a standby with standby controlfile

From: Stojan Veselinovski <>
Date: Tue, 11 Feb 2014 10:29:19 +1100
Message-ID: <>

Hi Don,

You can always go back to a basic restore instead of rman duplicate.  Restore the controlfile, catalog the remounted disk of the copy, switch and recover.

You may then need update the dbid, name and other config if need be. It will still let you use the backup as copy method and save some time.

Can be scripted.



On Tue, Feb 11, 2014 at 8:38 AM, Don Seiler <> wrote:

> OK I've played a little more with the duplicate steps (using target-less
> duplication with BACKUP LOCATION specification) and so far it seems to only
> work with backups, not with datafile copies. I'd like to keep using the
> datafile copy method as it saves time, and our database is nearly 25Tb.
> Creating a "backup as copy" of the database and remounting the disks saves
> us from having to backup and then restore the datafiles which would take
> far too much time.
> Like I said, this method works great but so far requires a primary
> controlfile. It's really only an extra step when we do the refresh from the
> standby side but I'd like to see if we can do it without having to do that
> step, just to simplify and script as much as possible.
> On Sat, Feb 8, 2014 at 1:46 PM, Don Seiler <> wrote:
>> Version is I'll explore the duplicate options. Anyone done it
>> with data file copies target than backup set? I'd rather not do active our
>> require connection to primary or standby other than the initial backup as
>> copy.
>> Thanks again.
>> On Feb 8, 2014 1:37 PM, "Niall Litchfield" <>
>> wrote:
>>> With the right version ( with a patch or then you can
>>> run active duplicate from a standby db.
>>> On Feb 7, 2014 9:54 PM, "Don Seiler" <> wrote:
>>>> Good afternoon everyone.
>>>> Trying to work through a process where I can make a copy of our prod
>>>> standby (plus archivelogs) and have it stand up as a new dev database. We
>>>> have the process working but only when we use a backup controlfile from the
>>>> primary. I know this is nothing new but thought by 11.2 we'd have some way
>>>> to make this work.
>>>> I did get it to work but only when the standby redo logs were also
>>>> preset for the new instance. Then I could run the "activate standby
>>>> database" which does a standby crash recovery and then I can open it.
>>>> Anyone know offhand if there is a way around that so that?
>>>> This is basically the process:
>>>> 1. backup as copy database include current controlfile
>>>> 2. backup as copy archivelogs
>>>> 3. Remount NFS share to dev box.
>>>> 4. Update dev pfile to point to controlfile copy on nfs share
>>>> 5. Startup mount
>>>> 6. Catalog datafiles on nfs share and switch to copy
>>>> 7. Catalog archivelogs on nfs share and recover database
>>>> 8. open resetlogs
>>>> With the standby controlfile I'd have to first activate it before I
>>>> could open it in step 8. Again that requires having the standby redo logs
>>>> there and I don't think it would be valuable to copy those without stopping
>>>> standby recovery which I don't want to do.
>>>> I was hoping with the archivelog recovery done in step 7 that the new
>>>> database would have all of the recovery it needs to allow me to open.
>>>> --
>>>> Don Seiler
> --
> Don Seiler
Received on Tue Feb 11 2014 - 00:29:19 CET

Original text of this message