onmode -Y

I've been monitoring a problem process, and issued an onmode -Y sessionid 1, for the session that process is using. When the process hit the next query, it output to the sqexplain.out.sessionid file. But now the process appears hung, and the onstat -g sql sessionid shows a new query, but there was no further output for that query in the sqexplain file. The query is an insert query, and nothing is going into the new table. It uses a cursor. So I'm thinking because there is no output in the sqexplain file, that means that somewhere the process is hung trying to prepare the statement. Does it mean anything to anybody that the new sql shows in an onstat -g sql but not in the dynamic explain file ? btw, I can see the thread doing reads, but nothing really happens. Thanks, floyd ======================== -<<Floyd Wellershaus>>- Database Administrator Unix Administrator email: fwellers@yahoo.com Home: 703-430-0805 Cell: 703-477-6045 ======================== http://www.one.org/

On Apr 13, 10:07 am, Floyd Wellershaus <fwell...@yahoo.com> wrote: > I've been monitoring a problem process, and issued an onmode -Y sessionid 1, for the session that process is using. > > When the process hit the next query, it output to the sqexplain.out.sessionid file. > > But now the process appears hung, and the onstat -g sql sessionid shows a new query, but there was no further output for that query in the sqexplain file. > > The query is an insert query, and nothing is going into the new table. It uses a cursor. So I'm thinking because there is no output in the sqexplain file, that means that somewhere the process is hung trying to prepare the statement. > > Does it mean anything to anybody that the new sql shows in an onstat -g sql but not in the dynamic explain file ? > > btw, I can see the thread doing reads, but nothing really happens. > > Thanks, > floyd > > ======================== > -<<Floyd Wellershaus>>- > Database Administrator > Unix Administrator > > email: fwell...@yahoo.com > > Home: 703-430-0805 > > Cell: 703-477-6045 > ======================== > > http://www.one.org/ Try using onstat -g stk <threadid> and getting the stack. If it's hung in the optimizer it should be pretty obvious if you want to post the output. Otherwise the stack should give you somewhat of an idea what it's currently doing. Jacques