cancel
Showing results for 
Search instead for 
Did you mean: 

Troubleshooting Lock Table Overflow error

0 Kudos

Hi,

Can someone explain me each values of the below enqueue statistics as reported in SM12?

Enqueue Operations 103055771

rejected 2009066

Error occured 327526

Dequeue Operations 21381539

Error occured 0

Dequeue All Operations 49049125

Cleanup Operations 7

Backup Operations 3860467

Read Operations 28391758

Compress Operations 0

Verify Operations 0

Records written 24376225

to the backup file 23919598

Lock Owner Table, Size 456627

Maximum Fill level 460

Current Fill Level 112

Size of Lock Arguments Table 456627

Maximum Fill level 456626

Current Fill Level 1387

Lock Entries Table, Size 456627

Maximum Fill level 456626

Current Fill Level 1403

Update, fill level at maximum 114

Current Fill Level 0

Time in Lock Table /Seconds 5353.672306s

Wait for Lock Table /Seconds 5273.102137s

Time in Lock Server /Seconds 10925.006514s

I have noticed that the below user has used most of the locks.

450 MYG00382 03:07:50 U 10/07 03:21:11 Nr_of_Locks:456526 Scope: 2 0 450

Will the number of lock entries correspond to lock arguments in the lock table/enqueue statitics?

There has been a lock table overflow error in our system and we need to figure out what has happended?

Can you please help?

with regards,

Arul

Accepted Solutions (0)

Answers (3)

Answers (3)

jayaprakash_m
Explorer
0 Kudos

Hi,

I am getting a similar error like you have mentioned

450 MYG00382 03:07:50 U 10/07 03:21:11 Nr_of_Locks:456526 Scope: 2 0 450

What was the root cuase of your issue, How did you resolve it?

0 Kudos

hello,

SAP Note 746138 describes how you could analyze this .

Most of the times the reason is:

- the lock table configuration is too small or

- an application sets lots of locks or

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

kind regards,

Mercedes

Former Member
0 Kudos

Hi

This is very common problem with MIGO (depends on nature of business)

Check if updates are happening properly

have a look at extras -diagnosis in sm12

There are two options . .

Ask the users to input less data or

Increase the size of enque/table_size

rgds

jalli

Former Member
0 Kudos

eEar All

how this enque size reflected the Lock Entries.

Regards,

jitendra.

Former Member
0 Kudos

The larger the size the more lock entries.

For example:

- lock table of 4096kb -> 5023 entries

- lock table of 358400kb -> 442540 entries

Cheers Michael

0 Kudos

hello Arul,

the maximum number of entries correspond with the size of the lock table though the overflow.

If it's a normal situation that user locks that number of entries you'd need to increase the enqueue table size otherwise

you might need to investigate why that user locks so many entries..

See SAP Note 426188

kind regards,

Mercedes