In dedicated configuration, when v$session.status is 'KILLED', its
corresponding row in v$process (where addr=v$session.paddr) is gone.
Oracle keeps minimum information around for the user to know what
happened after the session is killed, sort of like a zombie process on
UNIX that only keeps enough for the parent to find him and clean up.
In shared server configuration, v$session.paddr or v$process.addr is a
shared server (visible in v$shared_server). When a session is killed,
v$session.paddr immediately changes to a new value, to which there's no
corresponding row in v$process. The old v$session.paddr (or old
v$process.addr) stays because it's a shared server.
Yong Huang
yong321ATyahoo.com
Received on Fri Jan 21 2005 - 09:34:05 CST
