Analysis of Lock Table Overflows

Use

The maximum number of locks in the lock table is subject to an upper limit, which can be defined in a profile parameter. Parameter enque/table_size (see also The Most Important Profile Parameters for the Lock Concept) determines the size of the lock table in KB. You can determine both the maximum number and the current number of entries in the transaction using Extras/Statistics.

A lock table overflow can occur if:

·        The lock table is configured too small

·        An application sets a large number of locks

·        The update process is hanging and this is passing a lot of locks onto the update task.

Afterwards you can analyze which type of locks exist and which lock owners have contributed to the lock table overflow. A history function is provided for this purpose.

Features

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

·        The three lock owners with the most locks

·        The three lock arguments with the most locks

Activities

On the List of Lock Entries screen choose the menu option Extras → Top Capacity Used →

·        Current:

The current capacity used status is displayed.

·        History

The overflow history is displayed. The person responsible, his or her user name, the time, and the number of locks are listed.

For instance:

·        Delete History

The overflow history is deleted.