Re: onmode -Y
Hi,
a) the stack traces not showing more info may
be a platform dependent problem. I'm not sure
on which platform you are with this system ... ?
b) could it be that your system is running out of
(the system wide maximum of) concurrent open
file descriptors?
Or the oninit processes reach the process limit for
open file descriptors?
Usually I'd expect some kind of message, but
possible if all file descriptors are exhausted it
is then difficult to write such a message (anywhere).
Having many queries run with session specific
sqexplain settings can cause a lot of additional
files opened ...
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland GmbH
Chairman of the Supervisory Board: Hans Ulrich Märki
Board of Management: Martin Jetter (Chairman), Rudolf Bauer, Christian
Diedrich, Christoph Grandpierre, Matthias Hartmann, Andreas Kerstan
Corporate Seat: Stuttgart, Germany; Reg.-Gericht: Amtsgericht Stuttgart,
HRB-Nr.: 14 562 WEEE-Reg.-Nr. DE 99369940
informix-list-bounces@iiug.org wrote on 16.04.2007 12:43:04:
> Yea. That was all the stk showed however.
> We did a reboot this morning, ( standard Monday morning thing ), and
these are running great.
> So either some kind of memory problem, or during the day, something is
holding resources that causes this.
>
>
>
> ========================
> -<<Floyd Wellershaus>>-
> Database Administrator
> Unix Administrator
>
>
> email: fwellers@yahoo.com
>
> Home: 703-430-0805
>
> Cell: 703-477-6045
> ========================
>
> http://www.one.org/
>
> ----- Original Message ----
> From: "david@smooth1.co.uk" <david@smooth1.co.uk>
> To: informix-list@iiug.org
> Sent: Saturday, April 14, 2007 5:03:11 PM
> Subject: Re: onmode -Y
> On 14 Apr, 02:04, 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-
Hide quoted text -
> >
> > - Show quoted text -
>
> We need the function names below this in the output!
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list