Session is not getting killed.

[koshal]

When a row gets locked I querying the SID & Serial# from v$session and issuing the command ALTER SYSTEM KILL SESSION 'SID,SERIAL#' from system user.But the session most often does not get killed.Most of the times database needs to be shut down . Suggest alternative ways to get rid of the locks.

 

[THoey]

Are you sure that it is not getting killed or is just in the rollback process? Depending on what that session was doing, the rollback could take a bit of time... Terry
**************************
* General Disclaimor - Please read *
**************************
Please make sure your post is in the CORRECT forum, has a descriptive title, gives as much detail to the problem as possible, and has examples of expected results. This will enable me and others to help you faster...

 

[karluk]

A lot of times the "alter system kill session" command just marks the session to be killed. If it is busy, it won't actually get killed until it is finished.

On Windows systems an alternative that should work is the ORAKILL command. At a command prompt type

orakill sid threadid

The thread id can be obtained from v$process.spid via a query similar to the following:

select p.spid, s.osuser,
from v$process p, v$session s
where p.addr=s.paddr;