Actually, if you kill sessions which are being debugged , eg through Toad,
you end up killing the session but the debugger session still remains
attached. In this case you have a choice of rebooting your server or killing
the attached debugger by using the spid.
"NetComrade" <andreyNSPAM_at_bookexchange.net> wrote in message
news:3fd78eb8.85530546_at_nyc.news.speakeasy.net...
> From my experience, this is not always the case.. Sometimes a session
> would be done rolling back (if not at all), but still hang around,
> often holding up an MTS server... unfortunately, in those cases even
> an MTS server has to be killed.. recently filed a bug with Oracle.
>
> On Wed, 10 Dec 2003 09:10:02 -0800, Daniel Morgan
> <damorgan_at_x.washington.edu> wrote:
>
> >Giovanni Azua wrote:
> >
> >> Hello all,
> >>
> >> Is there really a way to KILL!!!! a session
> >> because the "marked for kill" can easily last
> >> couple of days, this thing is irritating being
> >> not preemptive at all.
> >>
> >> Best Regards,
> >> Giovanni
> >
> >A kill is a kill is a kill. What you are seeing is Oracle cleaning
> >things up. Leave it alone. You can not just leave behind a mess. The
> >changes must roll back.
> >
> >But if it is truly taking days ... likely you have other problems and
> >need to look to see what they are.
> >
> >--
> >Daniel Morgan
> >http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
> >http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
> >damorgan_at_x.washington.edu
> >(replace 'x' with a 'u' to reply)
> >
>
> .......
> We use Oracle 8.1.7.4 on Solaris 2.7 boxes
> remove NSPAM to email
Received on Thu Dec 11 2003 - 14:02:54 CST
