RE: Lock table overflow

Hi, "onstat -k" shows for which resource (database, table, index, row) the locks are used and who the owner is (the owner column is the address of the user thread). With the latter and the output of "onstat -u" you can determine the session ID of this user thread. Using that session ID with "onstat -g ses <session ID>" will show you, what the user is doing (SQL statement, etc.). At least if you find one particular session that needs the bulk of the locks you have found a culprit ... If you find that locks are evenly distributed among users (user sessions), then it is a bit more difficult. I'd then guess there was a change in the application ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Data Management Solutions owner-informix-list@iiug.org wrote on 18.01.2005 20:45:10: > I've got the same problem. In my case the lock table overflow was > preceded with 12 dynamic allocations of 100,000 locks. We start with > 300,000. So we are growing to 1,500,000. And it only takes 30 seconds. > Obviously we need more locks but I am reluctant to add that many as our > other similar sites have a lot less. The application is sales ledger > period end and in december worked fine with 300,000 locks but why the > sudden increase? > > Any ideas? > > Malcolm > > -----Original Message----- > From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] > On Behalf Of LUQUE Valdivia Omar > Sent: 18 January 2005 14:02 > To: informix-list@iiug.org > Subject: Lock table overflow > > > Hi everyone, > > I have observed that problem: > > 02:04:14 Lock table overflow - user id 1, session id 9425 02:04:14> Lock table overflow - user id 1, session id 9425 02:04:14 Lock table > overflow - user id 1, session id 9425 > > What Happend? > > Please, Help me > > Thanks > > > > Omar. > > > sending to informix-list > > sending to informix-list sending to informix-list