Re: backup
Date: Tue, 24 Feb 2015 14:34:49 -0500
Message-ID: <CAAaXtLBZ2qeYNN5rtJ2XFRfSmYMvCxjGXb3eqj1oAB=iLZkdoQ_at_mail.gmail.com>
If you altered the archivelog destination, then RMAN will be aware of where the archivelogs were actually written (even if you subsequently changed the destination back to its original value).
If you are doing backups with RMAN, then it should be sufficient to just run your backups as normal, WITHOUT attempting to move around any of your "displaced" archivelogs. RMAN will find the archvielogs and back them up as usual, even though some are in an unusual location.
If, however, you MOVED archivelogs after they were written, you will have a bit more of a mess on your hands. You will either need to move the archivelogs BACK to where they were written, or un-catalog and re-catalog with the correct locations.
On Tue, Feb 24, 2015 at 9:35 AM, Zelli, Brian <Brian.Zelli_at_roswellpark.org> wrote:
> I had a database that ran out of archive space, so I altered the archive
> location to get it going again.
>
> Now I want to back it up. Do I alter the archive logs back first or back
> it up as is and then alter the archive location
>
> back to where it was after the backup?
>
>
>
> Brian
>
>
>
>
>
> This email message may contain legally privileged and/or confidential
> information. If you are not the intended recipient(s), or the employee or
> agent responsible for the delivery of this message to the intended
> recipient(s), you are hereby notified that any disclosure, copying,
> distribution, or use of this email message is prohibited. If you have
> received this message in error, please notify the sender immediately by
> e-mail and delete this email message from your computer. Thank you.
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Feb 24 2015 - 20:34:49 CET