Re: shutdown immediate or abort for cold-backup?

Please let me get this straight.
A shutdown abort is equivalent to a crash, ie a power outage or whatever. Do you think you can make a backup of a database which is potentially corrupt and will be recovered automatically on the first startup after the shutdown abort.

You can't mean this seriously, can you?
In the first scenario when the startup restrict succeeds you have a working database.
In the second scenario you are going potentially to restore a database which is in recovery state.
Your backup can not be considered to constitute a consistent backup Your assertion there is no difference between the two scenarios is just plain nonsense

Regards,

Sybrand Bakker, Senior Oracle DBA

"Keith Boulton" <kboulton_at_ntlunspam-world.com> wrote in message news:8%of7.927$Qh2.2407_at_news11-gui.server.ntli.net...
> There is no effective difference wrt database corruption between:
>
> shutdown abort
> startup restrict
> shutdown immediate
>
> and
>
> shutdown abort
> backup the database
> restore the database
> startup restrict
> shutdown immediate
>
> What you are actually saying is that ANY use of shutdown abort carries the
> risk of corrupting the database. It's not much of a database if that is
the
> case.
>
> "Thomas Kyte" <tkyte_at_us.oracle.com> wrote in message
> news:8096153.0000d289.015_at_drn.newsguy.com...
> > In article <pXhf7.2923$0z.44549_at_news11-gui.server.ntli.net>, "Keith
> says...
> > >
> > >> You should not trust in a backup after a shutdown abort.
> > >
> > >Bollocks
> > >
> > >
> >
> > you know, just because something appears to work in a test or two does
not
> mean
> > that it works and is the right, proper thing to do....
> >
> > Ok, to be more clear:
> >
> > you should not trust a backup after a shutdown abort without a
> startup/shutdown
> > normal|immediate when in archivelog mode.
> >
> > A shutdown abort can result in fractured blocks. A fractured block is
> where the
> > head != tail of the block. In hot backup mode, we take special pains to
> avoid
> > this issue by logging additional information to the online redo log.
This
> > additional information won't be there in this case. Media recovery
could
> fail
> > (not will, could -- do you want to risk it? I don't)
> >
> > If you are in archivelog mode, don't shutdown abort and copy those
> files... do
> > a startup/shutdown normal|immediate and then copy them.
> >
> > If you are in noarchivelog mode -- make sure to backup your online redo
if
> you
> > do this (this is the ONLY time ever that you should -- nay have to --
back
> them
> > up, normally it is an error to back them up)
> >
> > --
> > Thomas Kyte (tkyte@us.oracle.com) http://asktom.oracle.com/
> > Expert one on one Oracle, programming techniques and solutions for
Oracle.
> > http://www.amazon.com/exec/obidos/ASIN/1861004826/
> > Opinions are mine and do not necessarily reflect those of Oracle Corp
> >
>
>
Received on Sat Aug 18 2001 - 07:48:38 CDT