Sap Profile Table Update Problems Exist

Here we have listed down some of the known problems and solutions for SAP enqueue lock table overflow.

The enqueue table size is controlled by the parameter enquetablesize.

The lock table contains information on which locks are currently held by whom.

Sap Profile Table Update Problems Exist

If no update problems exist, you can use this parameter to increase the size of the lock table.

First we can check the enqueue statistics from SM12 extras Statistics looking at the maximum fill level.

Here we can check top user which is causing enqueue lock table overflow and since when the lock table overflow is happened.

Based on this observation you can come to know which user causing the locks.

If it is a background user check if parallel running of same program or jobs causing such bottlenecks.

In this case you may see the following errors in the systems: Update not possible; event handler is locked (enqueued) (SAPTRXAPPLOG 017).

SAPTRXAPPLOG 017, SAPTRXAPPLOG017, SAPTRXPTA 059, SAPTRXPTA059, SAPTRXAPPLOG 105, SAPTRXAPPLOG105, lock, enqueue, lock table, overflow, saptrxbapiehpost, saptrxbapiehaddeventmsg02.

The setting must be made in the profile of the enqueue server (DVEBMXX ).

The change only takes effect after the restart of the enqueue server.

Sap Serial Number Profile Table