Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!crtntx1-snh1.gtei.net!nycmny1-snh1.gtei.net!news.gtei.net!newsfeed.mathworks.com!lon-transit.news.telstra.net!news.telstra.net!newsfeeds.bigpond.com!not-for-mail From: "Howard J. Rogers" Subject: Re: SQL Statement Shutdown User-Agent: Pan/0.13.0 (The whole remains beautiful) Message-Id: Newsgroups: comp.databases.oracle.server References: <1046683618.662160@ftp.adept.co.za> <3e6368db.22201921@read.news.fr.uu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Lines: 20 Date: Tue, 04 Mar 2003 06:11:41 +1100 NNTP-Posting-Host: 144.138.45.34 X-Trace: newsfeeds.bigpond.com 1046718154 144.138.45.34 (Tue, 04 Mar 2003 06:02:34 EST) NNTP-Posting-Date: Tue, 04 Mar 2003 06:02:34 EST Organization: Telstra BigPond Internet Services (http://www.bigpond.com) Xref: newsfeed1.easynews.com comp.databases.oracle.server:178291 X-Received-Date: Mon, 03 Mar 2003 12:13:14 MST (news.easynews.com) 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