Re: Hot backups : Catching the last Archived redo log at the end of the backup cycle.

It's been a long time since I worked with this (over 1 year ago), but I believe we dealt with this issue by issuing something like:

    alter system switch log file
    alter system archive log stop
    build a shell variable which has the contents of the archive directory in it

    alter system archive log start
    then back up the files listed in the shell variable

The theory was that
1. archive log stop would not execute until a the last log file was archived
2. building a shell variable containing all files in the archive destination is a quick process

        (i.e., the archiver would not be stopped for long)

Hope this helps
Steve

Rob Forster wrote:

> After one completes backing up their last tablespace, how can we be sure
> that when copying the last redo log we do not catch ARCH when its in the
> middle of archiving the last redo log?
>
> alter tablespace begin backup;
> ! cp etc.
> alter tablespace end backup;
> alter system switch logfile; -- arch starts archiving the latest redo log
> that was forced by this command
> ! cp ...
> -- are we going to be copying an incomplete archived redo log here?
>
> TIA,
> Rob.
Received on Tue Apr 07 1998 - 00:00:00 CDT