@Roachcoach, i understand after marked kill, then alter system kill session do nothing. But my main concern is in v$session it show killed for a longer time, how to kill those killed session. One way is os kill using kill -9 spid, but when i try to find out spid, i failed. I try to join with v$process for spid, but no row return for those killed session.

I also try to find out active transaction using v$transaction view, but v$transaction has no record.

 select * from v$process where addr=PADDR_FROMV$SESSION

I try to join with v$process for spid, but no row return for those killed session.

mmi

What Is the last_et_call for the killed session can you please paste me the output here.

Regards
kapardi

But if you want a quick reaction,it's better to kill it on os level, because it take time when the session was killed at db level and acctually,the session was not remove at all..

Quote:

But if you want a quick reaction,it's better to kill it on os level, because it take time when the session was killed at db level and acctually,the session was not remove at all..

No, it is not better and not faster.
In addition, it relies on exception trapping and handling which is always risky than the normal way.
As I said it is (or should be) the last resort.

Regards
Michel

i had also try to killed those killed session using immediate and record still get from v$session. and already 30 mins over but killed sessions still show in v$session. 30 minutes is not enough for clear it?