Skip to end of metadata
Go to start of metadata

How to check enqueue overflow?

The enqueue lock table overflow occurs if the number of lock requests is bigger than the limit of the enqueue table. It is limited by the parameter “enque/table_size”. The reasons for an overflow are explained in the note 13907.

13907  System error in the block handler, overflow lock table

If you are getting these messages in the syslog (SM21) or in the traces files you are facing an overflow in the enqueue table:

“Error locking table TBTCO”
“Lock table overflow”
“Internal lock administration error”
“internal error occurred in lock management”
“Enqueue: Transfer error  while reading lock entries”
*** ERROR => EqSet1(): GetFreeEntry() failed, EntryTable overflow
*** ERROR => EqSet1(): GetFreeUser() failed, user table overflow

The way to check if there is an overflow is via statistics of transaction SM12.
Go to “SM12 -> Extras -> Statistics” and you find statistics as per:

If the "Maximum Fill Level" exceeds “Maximum Number of Lock…”, then you are facing an enqueue overflow.
The enqueue table is stored in the runtime memory, so its statistics are from the last start up.

You can also analyse the enqueue statistics is from Operating System level with the sapcontrol tool.

Sapcontrol is a client tool that connects to the sapstartsrv service and works with web methods. With the available function “EnqGetStatistic” you can check the same statistics list as available in transaction SM12. The command syntax is:

 sapcontrol -nr <NR> -function EnqGetStatistics 

The <instance number> option must be the instance number of ENSA (standalone enqueue server) ABAP or JAVA. This function does not work with classical CI where the enqueue service is running in a  dialog instance.

Below is an example of the statistics collected with the sapcontrol:

To check the list of available functions, call the command sapcontrol and check the list of WEBMETHODS.

 

 

<back to FAQ section>