Re: Error 244 Fetch Error

>From: Dan Madvig - Bethel College & Sem. <daniel@genesis.admin.bethel.edu> >Date: Wed, 19 Apr 95 16:35:12 CDT >X-Informix-List-Id: <list.6033> > >> Error 244 (Could not do a physical order read to fetch next row) has >> been occurring more frequently in our application. It comes up during a >> fetch next row call. When we get the error, that particular query is >> incomplete; however subsequent queries work fine. We are even able to >> repeat the same query and it work fine on the second try. The error is typically transient -- someone else had a lock on something at an inconvenient moment. A rerun will therefore seldom run foul of the same error on the same row. >> Any ideas what could be causing the problem? > >Are you using SACEGO? As I understand it, there's a BUG in SACEGO. It >won't do DIRTY READs. Thus when someone has a row locked, your query >burps. Depending on the version of ISQL in use, SACEGO uses the SACEISOL environment variable to control the isolation. With versions 4.12, 4.13 and 6.00, 6.01 (and any future versions), the value can be any of the isolation levels 'committed read', 'repeatable read', 'cursor stability' or 'dirty read'. In 4.11, the only value was 'dirty read'. I am not certain whether it was available in either 4.00 or 4.10, but I think not. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h>