shutdown immediate: make it go faster

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Thu, 21 Nov 2002 17:51:12 -0000
Message-ID: <E2F6A70FE45242488C865C3BC1245DA702F5608C@lnewton.leeds.lfs.co.uk>

Charles,

shutdown immediate causes all outstanding transactions to be rolled back. If a transaction has been updating for half an hour, then it will take at least (?) half an hour to undo its changes. So, the 'immediate' part of shutdown immediate is a bit of a mis-nomer - ion certian cases.

You can save yourself having to kill everything manually by simply doing a 'shutdown abort' or better 'startup force' followed by 'shutdown'.

Cheers,
Norman.

PS. There is a faq on this over at http://jlcomp.demon.co.uk/faq/ind_faq if you want more details.

Norman Dunbar
Database/Unix administrator
Lynx Financial Systems Ltd.
mailto:Norman.Dunbar_at_LFS.co.uk

Tel: 0113 289 6265
Fax: 0113 289 3146
URL: http://www.Lynx-FS.com
-------------------------------------

-----Original Message-----
From: Charles J. Fisher [mailto:cfisher_at_rhadmin.org] Posted At: Thursday, November 21, 2002 5:05 PM Posted To: server
Conversation: shutdown immediate: make it go faster Subject: shutdown immediate: make it go faster

"shutdown immediate" takes a long time on some of my databases. I've never
really known why; disk activity is usually very low throughout the shutdown period.

However, if I kill all of the "oracleSID (LOCAL=NO)" processes prior to the the shutdown immediate, it goes a lot faster. I assume that this will
drive PMON nuts, but I don't see any other major risk.

I've killed these processes with:

ps -ef | awk '/oracle.*LOCAL=NO/ && !/awk/ {print "kill "$2}' | sh

Is this something that I should consider doing in non-emergency situations?

/ Charles J. Fisher | cfisher@rhadmin.org | http://rhadmin.org /

Received on Thu Nov 21 2002 - 11:51:12 CST