Re: shutdown immediate - waiting for active calls to complete

David J. DeWolfe wrote:
>
> Greetings DBA's
>
> Twice in the last two weeks (and 3 times in the last 2 months) a shutdown
> immediate has failed to shutdown one particular instance. The alert log shows
> the following message:
>
> SHUTDOWN: waiting for active calls to complete.
>
> and just waits and waits and waits......... until I do a shutdown abort.
> Whether or not it has something to do with it, each time i've seen this
> message it has been preceeded by several "found dead dispatcher" messages. I
> have a TAR logged with Oracle for this, but figured i'd check here as well.
> Anyone have any insight as to what may be happening? Specifics are:
>
> Oracle 7.1.4.1.1
> SQL*net 2.1
> Digital Unix 3.2C (formerly OSF/1)
> 95+ % connections via MTS

I've seen a similar problem with stray dispatchers on HP 9.x and 10.x with Oracle 7.1.6. It tends to leave dispatcher processes out there for some reason, even after the database is shut down. I usually just shut down the database, and then manually remove any stray processes with the database name in them.

I'm not sure what the problem is with the 'shutdown immediate'. According to the manual, when you do a 'shutdown immediate':

"Current client SQL statements being processed by Oracle are terminated immediately; any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)"

Could you possibly have some long transactions running, and you just need to wait longer for the databases to come down?

-- 
Brian M. Biggs                             mailto:bbiggs_at_cincom.com
Cincom Systems, Inc.                       voice: (513) 677-7661
http://www.cincom.com/