Re: onmode -Y

On Apr 13, 8:04 pm, Floyd Wellershaus <fwell...@yahoo.com> wrote: > First stack, while it was doing an insert to one table: > Stack for thread: 660906 sqlexec > base: 0x07000003989dc000 > len: 36864 > pc: 0x0000000100056518 > tos: 0x07000003989e2c70> state: running > vp: 4 > 0x0000000000000000 > > Next stack, when the process is hung, while it is doing an insert into another table ( and the last query is not in the explain.out. > > Stack for thread: 660906 sqlexec > base: 0x07000003989dc000 > len: 36864 > pc: 0x0000000100056518 > tos: 0x07000003989e2c70> state: running > vp: 4 > 0x0000000000000000 > > ======================== > -<<Floyd Wellershaus>>- > Database Administrator > Unix Administrator > > email: fwell...@yahoo.com > > Home: 703-430-0805 > > Cell: 703-477-6045 > ======================== > > http://www.one.org/ > > ----- Original Message ---- > From: "jpren...@yahoo.com" <jpren...@yahoo.com> > To: informix-l...@iiug.org > Sent: Friday, April 13, 2007 12:25:36 PM > Subject: Re: onmode -Y > > 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 > > _______________________________________________ > Informix-list mailing list > Informix-l...@iiug.orghttp://www.iiug.org/mailman/listinfo/informix-list Eh, I was expecting the thread to be in some yielded state, not running. Unfortunately onstat -g stk <threadid> is not reliable when run on a thread in a running state. You would have to use other methods to obtain that info. However, since it appears to have cleared up guess there isn't much to do now. But did want to let you know about the onstat -g stk issue on running threads for infomation purposes.

On 16 Apr, 15:24, jpren...@yahoo.com wrote: > On Apr 13, 8:04 pm, Floyd Wellershaus <fwell...@yahoo.com> wrote: > > > > > > > First stack, while it was doing an insert to one table: > > Stack for thread: 660906 sqlexec > > base: 0x07000003989dc000 > > len: 36864 > > pc: 0x0000000100056518 > > tos: 0x07000003989e2c70> > state: running > > vp: 4 > > 0x0000000000000000 > > > Next stack, when the process is hung, while it is doing an insert into another table ( and the last query is not in the explain.out. > > > Stack for thread: 660906 sqlexec > > base: 0x07000003989dc000 > > len: 36864 > > pc: 0x0000000100056518 > > tos: 0x07000003989e2c70> > state: running > > vp: 4 > > 0x0000000000000000 > > > ======================== > > -<<Floyd Wellershaus>>- > > Database Administrator > > Unix Administrator > > > email: fwell...@yahoo.com > > > Home: 703-430-0805 > > > Cell: 703-477-6045 > > ======================== > > >http://www.one.org/ > > > ----- Original Message ---- > > From: "jpren...@yahoo.com" <jpren...@yahoo.com> > > To: informix-l...@iiug.org > > Sent: Friday, April 13, 2007 12:25:36 PM > > Subject: Re: onmode -Y > > > 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 > > > _______________________________________________ > > Informix-list mailing list > > Informix-l...@iiug.orghttp://www.iiug.org/mailman/listinfo/informix-list > > Eh, I was expecting the thread to be in some yielded state, not > running. Unfortunately onstat -g stk <threadid> is not reliable when > run on a thread in a running state. You would have to use other > methods to obtain that info. However, since it appears to have > cleared up guess there isn't much to do now. But did want to let you > know about the onstat -g stk issue on running threads for infomation > purposes.- Hide quoted text - > > - Show quoted text - You can use pstack on the process to get the stack.