ISAM error: no more locks

I'm seeing some errors on our Informix 7 installation on Solaris 134 ISAM error: no more locks 244: Could not do a physical-order read to fetch next fow This is via some 3rd party software. What does this mean?

On Thu, 03 Jun 2004 05:25:57 -0400, Geezer From The Freezer wrote: > I'm seeing some errors on our Informix 7 installation on Solaris > > 134 ISAM error: no more locks > 244: Could not do a physical-order read to fetch next fow> > > This is via some 3rd party software. What does this mean? It means that your query was performing a sequential scan of some table(s) and either some other query/update/delete had used up all of the locks configured on the server or this query did due to the isolation level requiring a shared lock on all rows visited within a transaction. Solution? Increase the LOCKS in the ONCONFIG file, decrease the size of the query/transaction, add the missing index that caused a sequential scan, update statistics properly (per the Performance Guide recommendations) sothat existing indexes are used. Art S. Kagel