Re: lock table overflow

Check the lock mode of the tables in question. Change them all to page. Then you won't get so many locks. Of course this has serious implications on how record acquisition by the next fellow...... cheers j. satriguy@aol.com (SaTriGuy) on 02/26/98 08:36:31 AM Please respond to satriguy@aol.com (SaTriGuy) To: informix-list@iiug.org cc: (bcc: Jack Parker/Boston50/Epsilon) Subject: Re: lock table overflow >hi > >i'm running ods7.23uc1 on hp-ux10.20. this application is an off-the-shelf >manufacutrin gpkg which runs on top of informix. whenever a particular >trnasaction the application bombs out with the errors below: > %SQLCODE: -244 Could not do a physical-order read to fetch next row. > %SQLERRD2: -134 ISAM error: no more locks >and in looking at the log file , i saw this error: >19:13:32 Lock table overflow - user id 102, session id 47> >i'm wondering if anyone has any ideas on this. i did do oncheck on the tables >and indices the sql was after, and it came back okay. i'm attaching my Well - you're out of locks, but your lock table is rather large. Either this is a very large transaction, the isolation mode is "repeatable read", or you're using "MODE ANSI logging" Madison Pruet