Re: How to set the WHOLE Database in backup mode

drak0nian_at_yahoo.com (Paul Drake) wrote in message news:<1ac7c7b3.0304221633.67ee444e_at_posting.google.com>...
> Rick Denoire <100.17706_at_germanynet.de> wrote in message news:<frg8avcq7pigvia1qt6jpni7mcm9skvnff_at_4ax.com>...
> > Well we know the command "alter tablespace <tralala> begin backup",
> > but if there are a dozen of tablespaces, and one has to make a hot
> > Snapshot of the DB files, then I wonder if having to use this command
> > a dozen of times (for each tablespace separately) will garantee that
> > all tablespaces are in sync when the last of them is set in backup
> > mode.
> >
> > So is there any other command to set the DB as a whole in the backup
> > mode?
> >
> > Thanks
> > Rick Denoire
>
> sure -
> sqlplus /nolog
>
> alter system checkpoint;
> alter system archive log current;
> shutdown abort
> startup restrict
> shutdown immediate
>
> <run your cold backup job>
>
> startup
> quit
>
> you now have a consistent backup set - and you didn't even have to put
> any tablespaces in backup mode - and it won't require any recovery.
>
> if that it not what you wanted, then you must change what you want.
> "hot" or "consistent" are mutually exclusive concepts.
>

They are not. Any hot backup set is consistent if you: 1. Have current controlfiles or backup controlfile from the time later than last hot backup was taken.
2. Have all archived logs from the time before first file in the set was backed up.

You can easily have consistent backup set even if you do hot backup of one tablespace a day.

BTW, it's all described in documentation.

> Pd
Received on Wed Apr 23 2003 - 11:10:49 CDT