Most people agree that when shutdown immediate takes a long time, it
is either transactions being rolled back, or sort segments being
cleaned up. It could also be a number of other things, but most of
those things are done by PMON and SMON.
One thing I will recommend, for this reason and for
Rick,
By now, I hope your database is back in working order.
My guess as to why you could not shut down your database is that the Drop
Table command was still running.
I've seen these long-running DDL commands get started and just stick around
until they finish, even if you killed the sqlplus
Thanks everyone with the DROP TABLE ... and SHUTDOWN replies. This morning
is much better.
I was able to DROP tables I needed. The shutdown problem would not occur
even after the DROP
finally succeeded. I was in a position to do a cold boot of the server and
viola I was able to
shutdown and
Do you have the dbsnmp agent running? I certain versions of
Oracle it just would not go away. Not sure which versions though.
It is gone in 8i though.
-Original Message-
Sent: Thursday, October 04, 2001 2:25 PM
To: Multiple recipients of list ORACLE-L
Hi All,
It is one of those
