Correct value enque/table_size

[Former Member]

Hello,

We  are experiencing lock table overflow in our system and we would like to  adjust the parameter enque/table_size to fix the problem.

Currently,  enque/table_size was set to 32384. Based on other posts, i need to  monitor the  Enqueue Statistics via SM12 to come up with the value for  adjustments.

Can  you give me some light on how to read and interpret the values on the  enqueue statistics and what are our basis in order to come up with the  correct value for enque/table_size parameter?

Here are the values on enque stats in SM12. What do I need to  check on this details? Hope you can recommend correct value based on the  details below.

Enqueue Operations                    66448963
rejected                                         155572
Error occured                                          0
Dequeue Operations                    29174450
Error occured                                          0
Dequeue All Operations                11529320
Cleanup Operations                                  8
Backup Operations                          836571
Read Operations                            1737929
Compress Operations                               0
Verify Operations                                      0
Records written                               4802573
to the backup file                             4762144
Maximum Number of Lock Owners       40429
Maximum Fill level                                   90
Current Fill Level                                      23
Maximum Number of Lock Arguments  40429
Maximum Fill level                              20763
Current Fill Level                                      43
Maximum Number of Lock Entries       40429
Maximum Fill level                             20763
Current Fill Level                                     43
Update; Fill Level at Maximum                 35
Current Fill Level                                       0
Time in Lock Table /Seconds    2532.773472s
Wait for Lock Table /Seconds    582.543703s
Time in Lock Server /Seconds    3680.166150s

Thanks in advance.

Israel.

Enqueue Operations    66448963
rejected    155572
Error occured    0
Dequeue Operations    29174450
Error occured    0
Dequeue All Operations    11529320
Cleanup Operations    8
Backup Operations    836571
Read Operations    1737929
Compress Operations    0
Verify Operations    0
Records written    4802573
to the backup file    4762144
Maximum Number of Lock Owners    40429
Maximum Fill level    90
Current Fill Level    23
Maximum Number of Lock Arguments    40429
Maximum Fill level    20763
Current Fill Level    43
Maximum Number of Lock Entries    40429
Maximum Fill level    20763
Current Fill Level    43
Update; Fill Level at Maximum    35
Current Fill Level    0
Time in Lock Table /Seconds    2532.773472s
Wait for Lock Table /Seconds    582.543703s
Time in Lock Server /Seconds    3680.166150s

[former_member188883 · Accepted solution]

Hi Israel,

You need to look into following entries from sm12

Maximum Fill level                              20763

Current Fill Level                                      43

Hope this helps.

Regards,

Deepak Kori

[mercedes_fernandez]

Hello Israel,

the principal reasons for enqeue overflow are:

o  the lock table configuration is too small

o  an application sets lots of locks

o  the update hangs and, as a result, numerous locks inherited by the update task exist

when you get an enqueue overflow you need to check the file ENQHISOVR in the work directory of the instance where the enqueue server is located. There you could see if the reason is an application that set many locks, in that case you'd need to check  if it was misused or normal behaviour. In this last case you increase the table size.

In the statistics snapshot you copied it looks fine the size since the "Maximum Fill level" is             20763 and the maximun that can be reached is 40429

kind regards,

Mercedes

[Former Member]

I would suggest performing a test in test system to know the maximum no of locks happen at a  particular system for a big report. After that you can keep on increasing this parameter.

You also need to keep in mind the configuration of the system.

[former_member185239]

Hi Israel,

Please follow the below link

http://wiki.sdn.sap.com/wiki/display/SI/Enqueue

125041  Analysis of enqueue errors with enqueue logging

13907  System error in the block handler, overflow lock table

746138 Analyzing lock table overflows

http://wiki.sdn.sap.com/wiki/display/Basis/Enqueue+overload+-+collecting+and+analyzing+the+enqueue+l...

http://wiki.sdn.sap.com/wiki/display/Basis/Enqueue+Lock+FAQ

With Regards

Ashutosh Chaturvedi