Lock table overflow

[Former Member]

hai friend,

My task is to update the status of changed IDOCs., I am using the fn. mod. IDOC_STATUS_WRITE_TO_DATABASE to do this updation. But it the run time iam getting the error

"Lock table overflow". please give idea to solve this problem.

thanks.

Vinayak.

[Former Member]

see oss note 746138, it will help you in solving your problem

Symptom

This note describes the subsequent analysis performed to determine the cause of a lock table overflow.

Other terms

Enque, enqueue, lock table overflow

Reason and Prerequisites

The maximum number of locks in the lock table is subject to an upper limit that is set by profile parameters. The enque/table_size parameter determines the size of the lock table in KBs. You can use SM12/Extras/Statistics to determine both the maximum number and current number of entries.

A lock table overflow may occur if

the configuration of the lock table is too small

an application sets lots of locks

the update hangs and, as a result, numerous locks inherited by the update program exist.

Up to now it, subsequent analysis could not be performed to determine which lock types and which lock owners mainly contributed to the lock table overflow.

Solution

The kernel patch described here saves information about the cause of a lock table overflow. This information can be queried subsequently.

The kernel patch concerns kernel releases 4.6D, 6.40 and higher.

The following information is saved for the last 10 lock table overflows:

the 3 lock owners with the most locks

the 3 lock arguments with the most locks

Use transaction SM12 to query the raw information and the following selection data in particular:

Client: "#01"

User name: "#01_002"

Table: "#01_002"

Argument: "#01_002"

Furthermore, this information is stored in the ENQHISOVR file in the work directory of the enqueue server.

The overflow information is written as of the following kernel patch levels:

4.6D: 1856

6.40: 21

[Former Member]

This fm is failing because it finds that the idoc is already locked so it is not able to process this idoc. Check if oyu are explicitly locking this idoc anywhere.

[Former Member]

Are you calling the FM multiple times. It may be that this FM is doing the locking but not the unlocking. You could put in a break-point after the call and in a separate session, use SM12 to look at the locks.

Rob