Re: RMAN restore without new datafiles

From: David Barbour <>
Date: Mon, 16 Jun 2008 14:04:33 -0400
Message-ID: <>


Does this die after it's restored the first 74 datafiles, or does it bomb out during the "set newname" portion of the exercise?

If the first - two suggestions:
1. Try setting the time past the end of the backup so you ensure you get the archivelogs. I've had this happen before and this worked for me. 2. Also done this: After the first 74 are completed, mount the duplicate, create the datafiles, then finish with
allocate auxiliary channel dupdb1 type 'sbt_tape'; allocate auxiliary channel dupdb2 type 'sbt_tape'; set until scn 3945622264;
recover clone database;

   alter clone database open resetlogs;}

If the second, you'll probably have to restore to a point in time before the datafiles were created (which will probably use a different backup), then follow the steps in (2) above.

On Mon, Jun 16, 2008 at 12:50 PM, Allen, Brandon <> wrote:

> Why not just take a new full backup to capture the new files and then use
> that one for your refresh?
> If you can't, or don't want to, do that for some reason, then I think
> you could use RESTORE/RECOVER *TABLESPACE* (instead of DATABASE*) *for
> each of the tablespaces not affected by the new datafiles. You might even
> be able to restore the affected tablespaces by using the RESTORE/RECOVER *
> DATAFILE* commands for only the existing datafiles and then offlining the
> missing datafiles, but I'm not sure if that would work or not.
> Regards,
> Brandon
> Privileged/Confidential Information may be contained in this message or
> attachments hereto. Please advise immediately if you or your employer do not
> consent to Internet email for messages of this kind. Opinions, conclusions
> and other information in this message that do not relate to the official
> business of this company shall be understood as neither given nor endorsed
> by it.

Received on Mon Jun 16 2008 - 13:04:33 CDT

Original text of this message