On Oct 29, 1:40 pm, "Art S. Kagel" <art.ka...@gmail.com> wrote:
> On Oct 29, 9:45 am, "Ian Michael Gumby" <im_gu...@hotmail.com> wrote:
>
> > Here's an interesting situation.
>
> > Had a long running query that seemed to go no where. Like it got lost.
>
> Usually when this happens I've found that it's not really hung. Just
> doing something I didn't expect like table scanning
> when I expected an indexed search.
>
> First thing I do is watch the onstat -u for the session over time to
> see if the engine thinks that it's doing something. If that's not
> conclusive I'll run xtree on the server, attach to the session, and
> watch it run. Xtree is an under appreciated tool, IMHO.
>
> Art S. Kagel
>
> > Has anyone had that happen to them running IDS?
>
> > I mean I had to literally file a help desk ticket to get the DBA to clear
> > the thread.
>
> > I've never had that problem in either Sybase or IDS.
>
> > It was driving me bonkers and I had to give up on a multi-threaded python
> > app. Seems that Oracle's cx_Oracle isn't thread safe. (Ok cx_Oracle may not
> > be under Oracle...)
>
> > Just griping.
>
> > -G
on ten you have the nice onstat -g pqs <session-id> command to watch a
query.