Tags: cant, database, followssqlgtselect, kill, killed, locked, mysql, oracle, pid, serial, session, sid, sql, statusfrom, steps, vsessionwhere

Why the session can't be killed?

On Database » Oracle

1,296 words with 3 Comments; publish: Sun, 10 Feb 2008 00:24:00 GMT; (25093.75, « »)

Hi all,

Maybe some data was locked,So I try to kill the session. My steps as follows:

SQL>select sid,serial#,pid,status

from v$session

where program='PROGRAMNAME';

SID SERIAL# PID STATUS

-- -- -- --

57 1120 000DD ACTIVE

SQL>alter system kill session'57,1120';

at this time an error was handled ra-00030

the session not exist.

After that i try to use orakill,So i do this

d:\orant\bin>orakill ora8 000dd

The returned message is:...successfull....

But I retrieve the v$session again,the session ever exist.

So PLZ tell me the ideas. Thanx in advance.

Chrisrobin

null

All Comments

Leave a comment...

  • 3 Comments
    • Hi,

      Maybe the session has been killed did u see the status.

      The Session will be removed by the PMON.

      Regards,

      Ganesh R

      #1; Sun, 24 Feb 2008 11:23:00 GMT
    • Hi,

      Thank you all.

      After the command "orakill ora8 000DD" was executed,i repeat the selection and the status is active(the same sessionid but the serial# is different.).

      #2; Sun, 24 Feb 2008 11:24:00 GMT
    • Hi

      I am not sure that it is important but every time when I used this command I putted space after comma:

      alter system kill session '57, 1120';

      Sometime session remain int the list but in status 'KILLED'. It is not a problem because all resources locked from session are left.

      Regards

      null

      #3; Sun, 24 Feb 2008 11:25:00 GMT