DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Killing a session - serial#

  1. #1
    Join Date
    Feb 2001
    Location
    Bangalore, India
    Posts
    109
    When we are killing a user session, we use SID,SERIAL#. For any session, the SID is unique( I hope I'm not wrong). Then what is the need of using SERIAL# in ALTER SYSTEM KILL command?

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Why do you have to specify END IF instead of just END at the end of an IF statment. Because that's the way it is.
    Jeff Hunter

  3. #3
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    alter system kill session 'sid,serial#';

  4. #4
    Join Date
    Feb 2001
    Location
    Bangalore, India
    Posts
    109
    I think Jeff got very angry(kidding). I know that thats the way it is, but I wanted to know if it has any significance when killing a session, like does it refer to any OS resources.

  5. #5
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    I have issues. I can't help it.

    No, Serial# is not related to any system resources like Process ID. See http://download-west.oracle.com/otnd...157.htm#991798 for details...
    Jeff Hunter

  6. #6
    Join Date
    Aug 2001
    Location
    Waterloo, On
    Posts
    547
    In my opinion, its a double surety to ensure you don't kill the wrong session by mistake.

    Raminder Singh

    Oracle Certified DBA: Oracle 8i, 9i


    Mail me at raminderahluwalia@rediffmail.com.

  7. #7
    Join Date
    Jul 2000
    Posts
    521
    A single session (SID) can have many serial#.
    Especially if you are working in a distributed env and ODBC connectivities.

    That is why you are required to specify both.
    svk

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width