Re: shutdown abort & consistent=Y

This is not entirely correct. A shutdown abort does not perform a checkpoint and the buffers are not flushed prior to shutdown. This means any transactions in the redo buffer but not in the redo log file are lost. Also any transactions in the redo log file with the commit still in the redo buffer are rolled back. Basically this can be used but you need to know the state of your transactions.

Eric Hanson

Sean Fitzgerald wrote:

> you won't lose anything by doing a shutdown abort followed by a startup
> restrict because upon the startup, oracle does an instance recovery using
> the online redo logs. This is a safe practice as long as you know what is
> happening on your database when you shutdown abort. For example, if you
> shutdown abort while tablespaces are in backup mode then the db will
> complain (file xyz needs media recovery.....) upon restart and you will need
> to take each datafile out of backup mode manually in order to open the db.
Received on Wed Feb 03 1999 - 12:12:40 CST