Lock table

[Former Member]

My archival jobs continuously fails because of Lock table overflow even after increasing parameter enque/table_size and then bounced.

But in SM12 No lock entries found

Under SM12 EXTRAS -> STATISTICS OR DIAGONOSTIICS are inactive

Job logs as below...

Job started

Step 001 started (program ZRJJARC20, variant CLL4, user ID MINIO)

Archiving session 000078 is being created

Lock table overflow

Job cancelled after system exception ERROR_MESSAGE

Regards,

Peter

[Former Member]

Peter,

There are three main reasons for the lock table overflow as per SAP.

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.

Please check the SAP link below:

http://help.sap.com/saphelp_nw70/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/content.htm

Also, please check out the SAPNOTE: 13907 and check if your current enqueue table size is adequate (though you mentioned you have already increased the same).

Keep us posted on the status.

Regards,

Sujit.

[Former Member]

Hi Peter,

If the value is equivalent to Granule entries, this shows the possibilities of Lock Table Overflow in recent past.

Try SM12 --> Fill in "#01_002" for 'Table name', 'Lock argument', 'User name' and fill in "#01" for 'Client' to know more about lock table overflow.

From this you can find which program causing lock table overflow.

Thanks

Deepak