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

[S_Sriram · Accepted solution]

Hi Raj

1.  Could you share your SAP version details?

2. It may be problem in kernel level

    Kindly refer the SAP Note 746138 - Analyzing lock table overflows

1565578 - Lock Table Overflow

BR

SS

[former_member618864 · Accepted solution]

Hello Sriram,

Thanks for reply. I have already gone through this notes. With the nelp of Note "1565578 - Lock Table Overflow" we able to confirm lock overflow issue found on our environment.. I need to identify which program/user, made system to run in to overflow issue. Can you help where i can find application level with help of Txn/program..

Regards,

Raj

[Reagan · Accepted solution]

The notes provided by Sriram (especially 746138 - Analyzing lock table overflows) are the ones you need to follow. The lock table overflow information is stored in the ENQHISOVR file at the OS level. You can also check this file to see who and what was executed. Check this wiki page to know more - Enqueue - Application Server Infrastructure - SCN Wiki

RB

[former_member618864]

Hi,

Thanks All for your tremendous replies and quick turn- around.. Much appreciated all your efforts..Reagan Benjamin has given wiki link which i have been looking for..

Thanks once again all of you.

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

[Former Member]

Hi Raj,

- Checked the table on which the update was happening. if it is the same table then you need to run the statistics on the table.

- Checked the dialog work process status as well and how many dialog process were available at that time.

You can follow the link as suggested by Divyanshu.

With Regards

Ashutosh Chaturvedi

[divyanshu_srivastava3]

This is a quick reply.

I good blog that covers a lot.

Have a look  -  http://www.sap-perf.ca/sap-lock-monitoring-and-issues-analysis/

Regards,

[Former Member]

Please refer the link below.

http://scn.sap.com/thread/1710391

Go to SM12 choose the menu option Extras > Top Capacity Used> Current ,History

[former_member618864]

Hello Palanki,

I tried to check as stated in SM12--> Extras-->Current ,History.. My options are greyed out. Let me know how make options visible.