Re: Interrupted 4GL reports bringing Informix off-line

Question: If these are 'reports', and not update programs, are you setting your isolation to dirty reads first?? Depending on the type of report you are running, you may not care if you have dirty pages that you are reading. Therefore, it is far less likely that your sqlturbo processes would be in any critical section because they would only be reading either pages in the buffer or loading pages from the database to the buffer. A critical part of loading pages to the buffer is during the latch process used to control maniplation of the LRU queues. Perhaps by increasing your cache you can reduce the need to load pages to the buffer, thereby decreasing the amount of loading from the database to the buffers. John Callaway Representing only my own humble ideas, proceed at your own risk ----------------------------------------------------------------------------- In article <48t15l$1em@newdelph.rtsg.mot.com>, Liam Kenneally <kenneall> wrote: >Hi, > >On our test systems we have noticed that when running 4GL reports via 4GL/GX >or the command line, the OnLine (4.10) engine crashes intermittently when >interrupted (eg by Ctrl-C): > >The problem seems to be that the sqlturbo process is holding a latch on a >critical section when killed, but I don't really understand where the critical >section is in terms of the 4GL report code which is really just reading from >the database. > >The Administrator guide states that :"a critical section is a section of OnLine >code that must be performed as a single unit. OnLine designates critical >sections to maintain physical consistency in a way that is analagous to to the >way that transactions maintain logical consistency". > >We are in discussion with Informix tech. support about this but I would >be interested if any other users have encountered the problem and if so, >how it was resolved. > >The following was obtained from OnLine.log. > > >12:34:40 Process Aborted Abnormally: pid=4130 user=150 us=4040209c flags=1 >12:35:12 Process Aborted Abnormally: pid=4132 user=150 us=40402108 flags=21 >12:35:12 Process Aborted Abnormally (latch): pid=4132 user=150 flags=21 >12:35:12 INFORMIX-OnLine entering ABORT mode!!! >12:35:12 -- Online Aborting -- us=40401b8c, pid=4218, uid=0 >12:35:17 shmem sent to /usr/gsm/dumpdir/shmem.4218.ABORT. (OnLine Abort) >12:35:19 INFORMIX-OnLine Stopped> > >Any ideas ? > >Thanks in advance, > >Liam >