RE: ISAM error: no more locks

This error means, That some other session ahs locked the record in the table, this is why the first session is unable to read it. The workaround is either to increase 'SET LOCK MODE ..' period or make the operation at 'DIRTY READ' isolation level ------------------------------------------ Alexey Sonkin > -----Original Message----- > From: Geezer From The Freezer [mailto:Geezer@Freezer.com] > > very strange, informix has had locks increased from 200000 to 550000 > using onstat -k only 52000 max get used at any point. > logical logs increased 6 fold > KIAOON has been set to 1 > > Been seeing this too:- > > ISAM error: Lock Timeout Expired> Could not position within a table > > and > > ISAM error: No more locks> Could not position within a file via an index sending to informix-list