Lock Table Overflow

[former_member618864]

Hi,

We had an "Lock table overflow"  issue for 30mins in our production system.. Without performing any manual actions locks got cleared after 1hr.
Now, the requirement for us is to identify who has chewed up all the resources to cause lock table overflow.. is there any way, where i can able to find out which user/transaction/program has made to happen lock overflow.

I had gone through couple of Note, SAP Recomended to update enque/table_size to avoid this problem. But, without identifying reason we don't want to increase the parameter. As, well as i also checked in STAD. But, i unable to find the exact information. Thanks in Advance.

Regards,

Raj

[srinivasan_vinayagam]

Hi Raj,

Reason and Prerequisites for Lock Table Overflow:

1.     The lock table is configured too small

2.     An application sets a large number of locks

3.     The update process is hanging and this is passing a lot of locks onto the update task.

4.     Running a  report with improper selection criteria (like very long time periods data pull) which sets         so many locks & eventually lock table overflow occurs.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0869e29-1405-2e10-27be-db1dad770...

Before changing the parameter analysis to find out the reason

1565578 - Lock Table Overflow

Regards,

V Srinivasan

[Former Member]

Hi Raj,

The options are disabled as you enter SM12 and entering the user as * and then going to lock entry screen that is the reason the options are disabled. just go to transaction sm12 you will see the EXTRAS option there as well and that would be enabled.

Thanks