Re: killing a 'killed' session

Tom wrote:
>
> "NetComrade" <andreyNSPAM_at_bookexchange.net> wrote in message
> news:3e7a439a.2094599024_at_nyc.news.speakeasy.net...
> > where sid is the sid of a session you're trying to kill (from
> > v$session).
> >
>
> SID SERIAL# USERNAME ROUND(LAST_CALL_ET/60)*60 IDLE
> ---------- ---------- -------------------- ------------------------- -------
> -
> 13 11567 XXXXXXX 1057440 KILLED
>
> select p.spid
> 2 from v$process p, v$session s
> where s.paddr = p.addr
> 3 4 and s.sid = &1
> 5 ;
> Enter value for 1: 13
> old 4: and s.sid = &1
> new 4: and s.sid = 13
>
> no rows selected
>
> ?

If there is no associated process then its probably already been killed. The session details hang around because there might be work to be done before the session can be 'discarded' (commonly undo)

hth
connor

-- 
=========================
Connor McDonald
http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue"