Lock table overflow (enque/table_size)

[Former Member]

Hi Expert,

I have read the SAP notes about lock table flow and it is mentioning to look at the statistics on SM12.

Below is the sample statistic:

Enqueue Requests.....: 213416

Rejects...........: 8912

Errors............: 275

Dequeue Requests.....: 72850

Errors............: 0

DequeueAll Requests..: 38719

CleanUp Requests.....: 1

Backup Requests......: 7740

Reporting Requests...: 47827

Compress Requests....: 0

Verify Requests......: 0

Writes to File.......: 111901

Backup............: 93554

Owner Names..........: 18347

Peak Util.........: 50

Actual Util.......: 4

Granule Arguments....: 18347

Peak Util.........: 18346

Actual Util.......: 9

Granule Entries......: 18347

Peak Util.........: 18346

Actual Util.......: 9

Update Queue Peak....: 20

Actual ...........: 0

Total Lock Time......: 9.216457s total

Total Lock Wait Time.: 34.570783s total

Total Server Time....: 9.966474s total

From this information, what should be my reference for the new value of enqueu/table_size?

Thanks in advance

[Former Member · Accepted solution]

hi Eida,

you set the parameters;

abap/buffersize : Program Buffer Size

1500000

enque/table_size

96000

ipc/shm_psize_10

600000000

ipc/shm_psize_40 Size of shared memory segment

250000000 byte

ferhan

[Former Member]

Hi Eida,

I'd start with the Peak Util and work from there. But it also begs the question of what job or transactions is causing this many locks. Is there a bunch of data coming in via RFC, batch upload or anything similar that might cause something like this?

I've seen simular situations occur where background jobs that load similar data sets are running at the same time.

J. Haynes

[Former Member]

Hi Joe,

Thanks for the feedback.

The problem that I had is one of the SD t-code -> VBOF is failing due lock table overflow. Now I've set the enque/table size to the maximun value (10MB).

Not sure if this parameter (enque/table_size) can be extend more the the advice max value. Any idea?

[Former Member]

Now I've set the enque/table size to the maximun value (10MB).

Did you mean 100mb? Because the documented max value is 102'400kb. But it could be set higher, read this thread:

But you should first fix the problem, if a single transaction is causing 1000+ locks, then this is almost everytime an application error. Please have a look at these notes:

[1043365 - SDBONT06: Error in lock management|https://service.sap.com/sap/support/notes/1043365]

[773247 - SDBONT06 causes lock table overflow|https://service.sap.com/sap/support/notes/773247]

Best regards, Michael

[Former Member]

Hi,

Can I know in what system do you set the enque size to 2GB. I've tried on R3 4.7 ext set 2 32 bits today, and the system had a problem with lock mechanism. When setting it from RZ10 and do a parameter check, it indicates that the value of 2GB is an error.

Now, I'm wondering how do you set the value bigger than the advice max size (100MB). Please clarify.

Edited by: Eida Hanafiah on May 5, 2009 2:31 PM

[former_member187565]

HI,

Have u check the sap note 13907 & Note 746138 - Analyzing lock table overflows

Have you restarted your system after increasing the parameter enque/table_size.

[Former Member]

Could the problem due to limitation of 32 bits and it can only have the size of 100MB for the enque/table_size?

[Former Member]

32-bit? Nah, don't think so, but the only system we have a size larger 100mb (it is in fact 200mb) is 64-bit.