Re: SQL Statement Shutdown

From: Howard J. Rogers <howardjr2000_at_yahoo.com.au>
Date: Tue, 04 Mar 2003 06:11:41 +1100
Message-Id: <pan.2003.03.03.19.11.40.446603@yahoo.com.au>

On Mon, 03 Mar 2003 14:40:47 +0000, Patrice Castet wrote:

> what do you want to shutdown ? the database ? a dispatcher ?
> by the way "shutdown abort" is like you "kill" your database, it has
> to perform a recovery when restarting !
> I advice you to use "shutdown immediate" which stop it cleanly instead
> of "abort". The "abort" option must not be used except for emergency
> issues.
>

Provided you have protected yourself against the loss of your current redo log by appropriate multiplexing and mirroring, there is zero risk in doing shutdown aborts. They are functionally equivalent to shutdown immediates, in the sense that both cause you to lose uncommitted transactions, and both preserve all committed transactions. There is nothing inherently dangerous or naughty about shutdown abort, and they are perfectly OK to use in situations which don't count as an emergency.

Regards
HJR Received on Mon Mar 03 2003 - 13:11:41 CST