In article <4296139b$0$22991$ba620e4c_at_news.skynet.be>, Matthias Hoys
says...
> > The session shows in OEM as "KILLED" but still holds a number of locks
> > and won't go away. Also I would expect a disconnect of the client to be
> > forced with a message such as "your session has been killed" (cannot
> > remember the precise wording but I am sure you know the sqlplus message
> > I refer to) plus an ORA-3114 not connected to oracle. But the client
> > reports nothing and appears to be unaware that the server proces is
> > killed.
> >
> > So if the client has not had its server session killed (which I assume
> > is in fact the case), what could cause this - OEM still shows the
> > session but with status KILLED.
> >
> > Appreciate any hints as this is rather perplexing!
> >
>
> The session is never cleaned up or does it take a long time ? It's probably
> doing a rollback of the modified data blocks ?
>
No it wasn't rolling back - it was actually waiting for a response from
an external proc that it was running via a java stored procedure.
--
jeremy
Received on Fri May 27 2005 - 01:46:59 CDT
