That user/session is not necessarily the user who is causing the lock table
overflow. Assuming you have enough locks configured on your server for
normal operations, then some user is doing a mass update, insert or delete
that is overflowing the lock table. Use onstat -k to identify that user.
Or use the this sql to query sysmaster:
select username,sid,pid,count(pid) from syslocks, syssessions wheresyslocks.owner = syssessions.sid group by username,sid,pid;
Regards,
Bill
> -----Original Message-----
> From: Azeemuddin, Basheer [SMTP:bahmed@KNRQ.com]
> Sent: Thursday, January 22, 2004 12:24 PM
> To: informix-list@iiug.org
> Subject: Lock table overflow - user id 283, session id 20458
>
> What should I do to get rid of this problem
>
>
> Thanks
> Basheer
> sending to informix-list
sending to informix-list