I did some research according to this issue before. Here is from my notes(I don't know where I got it, but must from one of the Oracle experts):
when a session is killed, oracle needs to rollback whatever work it had been doing - that's why it waits.
going to the o/s and killing the processes won't speed this up. However, when you use "alter system kill session", the session doesn't know it's killed until it makes another request to the database - if it was waiting for a response (particularly to a remote operation), it may not make a request for a long time, in which case killing the process from the o/s may help to stop the session. at that time, the database still needs to rollback whatever had happened already.
Sarah
-- --Original Message-- -- From: Yongping Yao [mailto:yaoyongping@(protected)] Sent: Thursday, September 15, 2005 11:06 AM To: Chen, Sarah Cc: Thomas.Mercadante@(protected); chiragdba@(protected); Oracle-L Freelists Subject: Re: Session Killed...!!
I agree that it's very strange to kill a session in Oracle. As I experienced, SELECTs are more easier to kill than DMLs and SELECTs running after a long time are more difficult to kill. UPDATE is the most difficult to kill. Oracle always reponds as "we have marked the session killed" but the session is still there and the lock remained hold. Anyone with good recommendations?
2005/9/15, Chen, Sarah <Sarah_Chen@(protected)>: > > I always check process id as well as sid and serial# while killing a session > from Oracle. > > I will always query v$session before and after, and if the status of > v$session marked "killed", and then I will go ahead kill OS process to clean > this session. It always works on Solaris. > > Sarah > > > -- --Original Message-- -- > From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]On > Behalf Of Mercadante, Thomas F (LABOR) > Sent: Thursday, September 15, 2005 10:47 AM > To: chiragdba@(protected); Oracle-L Freelists > Subject: RE: Session Killed...!! > > > > > If you kill the unix process associated with this session first, and then > the session it will go away. > > > > Killing sessions in Oracle has always been weird. Sometimes they go away > and sometimes not, depending on OS. In Windows, use orakill to kill the > session ??C this always seems to work in windows. And killing the unix > session then the Oracle session seems to work just fine in AIX. > > > > __ ____ ____ ____ ____ ____ ____ > > > From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)] > On Behalf Of Chirag DBA > Sent: Thursday, September 15, 2005 10:36 AM > To: askdba@(protected); Oracle-L Freelists > Subject: Session Killed...!! > > > > > Hi , > > > > > > I saw many users on my database connected for more than 6 days without any > activity. > > > > > > I killed 1 user and still the status in v$session is showing as killed. > > > > > > but it it not getting removed from the v$session. > > > > > > I am running 9.0.1.3 on solaris. > > > > > > any idea? We already hit the bug ora-07442 (See ora-07442.ora-code.com). > > > > > > regards - chirag
-- Yao Yongping Learning Oracle, UNIX/Linux... Love Reading, Classical Music, Philosophy, Economics etc. Blog: http://blog.csdn.net/ern http://spaces.msn.com/members/yaoyp/ -- http://www.freelists.org/webpage/oracle-l
