Skip to Content

Lock Table Overflow

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    Posted on Dec 10, 2014 at 03:26 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 10, 2014 at 02:37 PM

    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,

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 10, 2014 at 02:50 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 10, 2014 at 04:39 PM

    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-db1dad7703c5?QuickLink=index&…

    Before changing the parameter analysis to find out the reason

    1565578 - Lock Table Overflow

    Regards,

    V Srinivasan

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • Posted on Dec 10, 2014 at 04:57 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.