Re: shutdown immediate: make it go faster

Yes..use Shutdown abort - then startup - then shutdown normal.. ( this is generally safe and has even been recommended by Oracle Support, altho' any uncommitted transactions will be lost and there will be some cleanup by Oracle on startup..It usually is quite fast, however)

Remember that shutdown immediate will wait for uncommitted transactions to complete and will do other 'housekeeping' tasks that may take a long time ( forever, if some running Pl/Sql loop is badly formed and keeps updating some table) , depending on what is going on when you issue the command.

"Charles J. Fisher" <cfisher_at_rhadmin.org> wrote:

>"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?
>
> -----------------------------------------------------------------------------
> | The Moving Finger writes; and, having writ, |
> | Moves on: nor all your Piety nor Wit |
> | Shall lure it back to cancel half a Line, |
> | Nor all your Tears wash out a Word of it. |
> | |
> | -Rubaiyat of Omar Khayyam |
> -----------------------------------------------------------------------------
> / Charles J. Fisher | cfisher@rhadmin.org | http://rhadmin.org /
>-----------------------------------------------------------------------------
Received on Thu Nov 21 2002 - 11:50:52 CST