session marked for kill

From: Daiminger, Helmut <Helmut.Daiminger_at_KirchGruppe.de>
Date: Fri, 09 Nov 2001 02:05:09 -0800
Message-ID: <F001.003C0925.20011109014520@fatcity.com>

Hi!

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.

Thanks,
Helmut Received on Fri Nov 09 2001 - 04:05:09 CST