cancel
Showing results for 
Search instead for 
Did you mean: 

Lock table

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

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
0 Kudos

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

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

I think you are trying this option in SM12 after displaying the list of lock entries and because of that these options are grayed out.

Please go to SM12 and don't click on List. And then try these options, then these options will be visible and you can select that as well.

Thanks

Sunny

Former Member
0 Kudos

But i want to know why job fails even after clear lock entries in SM12.

Below find statics of locks

Enqueue Operations 42726

rejected 47

Error occured 1

Dequeue Operations 4349

Error occured 0

Dequeue All Operations 3735

Cleanup Operations 0

Backup Operations 2

Read Operations 5

Compress Operations 0

Verify Operations 0

Records written 29182

to the backup file 4

Maximum Number of Lock Owners 25311

Maximum Fill level 8

Current Fill Level 6

Maximum Number of Lock Arguments 25311

Maximum Fill level 25310

Current Fill Level 6

Maximum Number of Lock Entries 25311

Maximum Fill level 25310

Current Fill Level 6

Update; Fill Level at Maximum 1

Current Fill Level 0

Time in Lock Table /Seconds 2.876618s

Wait for Lock Table /Seconds 0.736393s

Time in Lock Server /Seconds 0.000000s

Former Member
0 Kudos

But i want to know why job fails even after clear lock entries in SM12.

Below find statics of locks

Enqueue Operations 42726

rejected 47

Error occured 1

Dequeue Operations 4349

Error occured 0

Dequeue All Operations 3735

Cleanup Operations 0

Backup Operations 2

Read Operations 5

Compress Operations 0

Verify Operations 0

Records written 29182

to the backup file 4

Maximum Number of Lock Owners 25311

Maximum Fill level 8

Current Fill Level 6

Maximum Number of Lock Arguments 25311

Maximum Fill level 25310

Current Fill Level 6

Maximum Number of Lock Entries 25311

Maximum Fill level 25310

Current Fill Level 6

Update; Fill Level at Maximum 1

Current Fill Level 0

Time in Lock Table /Seconds 2.876618s

Wait for Lock Table /Seconds 0.736393s

Time in Lock Server /Seconds 0.000000s