Re: RMAN duplicate question regarding archivelog file locations on different server
- From: Bradd Piontek <piontekdd@xxxxxxxxx>
- To: ChrisDavid.Taylor@xxxxxxxxxxxxxxx
- Date: Mon, 4 Oct 2010 13:46:17 -0500
Chris,
What does your duplicate command look like? (are you restoring to an SCN?)
By default , iirc, DUPLICATE will attempt to restore to the most current SCN
on the 'target' database. As a previous email stated, log_archive_dest_<n>
and log_archive_format will tell your auxiliary database where to look for
archivelogs (and where to restore them to). it sounds more to me like you
are duplicating to a point in time too current (unless you manually copy or
back up the archivelogs).
I tend to get an SCN from the latest backup controlfile and use that as my
DUPLICATE TO SCN number.
Bradd Piontek
On Mon, Oct 4, 2010 at 10:55 AM, Taylor, Chris David <
ChrisDavid.Taylor@xxxxxxxxxxxxxxx> wrote:
> I’m running a duplicate command to clone a database over to a dev server
> and the disk drive letters are different on the secondary server for the
> archivelogs. My backup disk location is the same on both servers.
>
>
>
> Is there a way when doing a duplicate to tell RMAN to look in an alternate
> location than where the primary sends its archivelogs?
>
>
>
> I’m receiving the RMAN-06025: no backup of log thread 1 seq 93814 lowscn
> 8775725044 found to restore error since the archivelog paths are different.
>
>
>
> To get around this, I’ve backed up the archivelogs on the primary and
> copied those backups and I believe the restore will work from that point but
> it seems like there should be an easy way to have alternate file locations
> when doing a duplicate.
>
>
>
> Thanks,
>
>
>
> *Chris Taylor*
>
> *Sr. Oracle DBA*
>
> Ingram Barge Company
>
> Nashville, TN 37205
>
> Office: 615-517-3355
>
> Cell: 615-663-1673
>
> Email: chris.taylor@xxxxxxxxxxxxxxx
>
>
>
> *CONFIDENTIALITY NOTICE: This e-mail and any attachments are confidential
> and may also be privileged. If you are not the named recipient, please
> notify the sender immediately and delete the contents of this message
> without disclosing the contents to anyone, using them for any purpose, or
> storing or copying the information on any medium.*
>
>
>
Other related posts:
