Re: Shutdown immediate - not quite as immedaite as I want it

Why not just do a shutdown abort?

Killing the listener just stops new connections from connecting but that doesn't help the people who are already connecting and actually modifying your database.

Shutdown immediate does take some time sometimes but I would advise that you let Oracle shutdown how it feels. Now if it is locking up completely, well that is a different story.

At 05:57 AM 5/25/00 -0800, you wrote:
>
>> I have some other problem though, in which I would like your advise.
>> Sometime there are still procedures running when the batch kicks in and
>> tries to do a shutdown immediate. Most of the time, the proces still
running
>> get's killed and the database is shut down. However, in some cases this
does
>> not happen, and the procedure just keeps running.
>
>Kirsten,
>
>I have found that if I shutdown the listener, run a kill session dynamic
>script that doesn't include oracle, sys, or system I have gotten just
>about everything dealt with before I execute a shutdown immediate.
>
>If you find something that involves less steps, please let me know. It'd
>be great to find out too.
>
>Thanks,
>
> Heidi :)
>
>--
>Author: Heidi E. Schmidt
> INET: heidi_at_cybercom.net
>
>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
>San Diego, California -- Public Internet access / Mailing Lists
>--------------------------------------------------------------------
>To REMOVE yourself from this mailing list, send an E-Mail message
>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
>the message BODY, include a line containing: UNSUB ORACLE-L
>(or the name of mailing list you want to be removed from). You may
>also send the HELP command for other information (like subscribing).
Received on Thu May 25 2000 - 10:16:11 CDT