Re: Lock manager out of room

The lock manager's memory requirements should not increase
continuously. Please post the header statistics from your database.
Also, use Performance Monitor to determine the age of the oldest active
transaction and post that. I suspect that you have transactions that
are never committed and that those transactions are holding locks.

-- 

Bill's answer is right on the money here. Let me add one more thing. You 
can run iblockpr to see what your usage is. The usage of iblockpr is 
documented in the Operation Manual. You'll probably just want the -h switch.

Bill Todd [TeamB] wrote:
> The lock manager's memory requirements should not increase
> continuously. Please post the header statistics from your database.
> Also, use Performance Monitor to determine the age of the oldest active
> transaction and post that. I suspect that you have transactions that
> are never committed and that those transactions are holding locks.

A few of our users frequently had at the end of a workday 'Lock manager out 
of room'. OK, that's an easy one the solve. I just change the parameter 
V4_LOCK_MEM_SIZE in the ibconfig file. According to information found on the 
Internet, it should be sufficient to change it from 98304 to 198304. And 
indeed then problem was solved. But a few days later the error occurred 
again. So I changed it to 300000. Problem solved again. A few weeks later. 
'Lock manager out of room'. At the moment the value of the parameter is 
500000 and I didn't get the error for now.
I think that it isn't normal that the parameter should be at this level. The 
program runs in a network but I guess that there are max. 100 queries 
opened. Is there a rule about the number of opened queries and the size of 
the lock file? Or is there a way to avoid the use of large locking-space?