Could be a bunch of things. Here's one thing I noticed in a development database yesterday (8.1.7.1.1 on Windows 2000)
Stored procedure issues an "analyze table compute statistics". In the alert log there was an ORA-00600 caused by the analyze (and also a trace file in udump.) However the procedure never returned the ORA-00600 and was "hung" all night. When I came in the next morning and checked session waits (using the session_times.sql script from the ixora website) I saw that it was waiting on "library cache load lock". An "alter system kill session" returned ORA-00031 (session marked for kill) but the numbers for the "libary cache load lock" wait kept on going up and the sesson didn't disappear. I had to use orakill at the OS level to stop the session.
-----Original Message-----
From: Daiminger, Helmut [mailto:[EMAIL PROTECTED]]
I got a call from one of our developers and was told that his app was hung on the dev box. So I issued an "alter system kill session" command. It took about 30 seconds then I got the message: session marked for kill.
But the connection still showed up in v$session, even after 5 minutes it was still there. Then I decided to shut down the db (which was ok since he was the only developer on the box): immediate didn't work (i.e. it took about 3 mins and nothing happened), so I issued a shutdown abort and restarted the instance.
Any idea what was going on? Why did it take so long? Was it all rollback activity?
This is 8.1.7 on sun Solaris.
