Lock table overflow

In a system when ever a user performs any update on any table for that period of time a lock on that particular field of that table is created so that no other user can update that table as user one is doing update on that table.
And Suppose during the update user session get terminated due to some error then this lock entry remains on that field.

 

lock table overflow

 

A lock table overflow can occur if:

• The lock table is configured too small
• An application sets a large number of locks
• The update process is hanging and this is passing a lot of locks onto the update task.
• Running a  report with improper selection criteria (like very long time periods data pull) which sets so many locks & eventually lock table overflow occurs.

How to identify lock table overflow issue ?

 

 

In SM21 transaction log and ST22 dumps, if you find any error messages like LOCK_TABLE_OVERFLOW, Lock table overflow, Internal lock administration error it means there is a lock table overflow issue.By these dumps we can get the idea .

 

 

What is the parameter to be changed to increase lock table size in SAP ?

 

Parameter enque/table_size to be changed to increase or decrease lock table size using RZ10 transaction. Default value of this parameter is 32768. The min value that can be set is 4096 and max value is 102400. The unit for this parameter is KB.

 

 

How to resolve lock table overflow ?

 

• Increase the size of lock table i.e increase the parameter enque/table_size value using RZ10 transaction.

  To determine the optimal value for this parameter, you can check the maximum locks set so far in the history and the current number of locks set from SM12 -> Extras -> Statistics 

 

• Increase the number of enqueue workprocesses