Re: backup without archivelog mode

"Sean M" <smckeownNO_at_BACKSIESearthlink.net> wrote in message news:3C9C9DE5.1DFB84DB_at_BACKSIESearthlink.net...
> "Howard J. Rogers" wrote:
> >
> > Archivelog mode simply means that you can guarantee recoverability of
all
> > transactions.
>
> Except for nologging transactions.
>

True enough, though there isn't a nologging transaction in existence which cannot be recovered by some other means (index rebuilds, for example). The database simply ignores the nologging keyword for anything which couldn't possibly be recovered (such as regular DML). So even a nologging transaction *is* recoverable.

> > But: You can never, ever make a copy of any database file whilst the
> > database is running, without that copy being internally inconsistent.
>
> Except for datafiles belonging to read-only tablespaces.
>
> > If you want to take hot backups (which your use of the 'alter tablespace
> > Florence begin backup' command suggests you want to do) then you will
> > absolutely, positively have to be in archivelog mode. There is no
exception
> > to the rule that hot files cannot simply be copied.
>
> Except for datafiles belonging to read-only tablespaces.
>

Be definition, read-only tablespaces are not hot.

HJR
>
> Regards,
> Sean
Received on Sat Mar 23 2002 - 14:45:35 CST