Re: oracle killed session still holding locks

I've seen this problem on several versions of Oracle, and on at least 3 platforms.

First off, the only option you have to get rid of the session is to bounce the instance.

Second, never kill a session with 'alter system kill session'.

You have the right idea with the kill -9, but in cases where you have an session with table locks that has been killed in Oracle, it will be ineffective. You need to do kill -9 first.

I've never determined how to reproduce this problem, and without a test case, there is little point in submitting it to Oracle.

I would suggest you start using kill -9 to kill sessions.

Whenever I suggest this, I always catch a lot of flack for it, but experience has shown it to be correct.

Jared

"Jean" <test_at_est.com> wrote in message news:<3810FD4EAD8AD611A50D00805F0DA7FA066B2A27_at_proxyusinor.usinor.com>...
> Hi,
> i'm new to oracle,
> the version is 9.2 aix 5.1 64 bit
> I've killed a session, it's been 9 days since.
> It's still marked as killed in v$session
> after that i've killed the pid in unix by kill -9 <pid>
> The session is still here holding locks on one table.
>
> What can i do to get rid of this ?
>
> Are there any comands to show me what this session do, how many io, cpu
> (like sp_monitor in sybase) ?
>
> thx for help
Received on Tue Nov 02 2004 - 13:08:21 CST