eG Monitoring
 

Measures reported by EnqueueTest

The Enqueue service allows SAP R/3 applications to lock data so that only they can use it. Locking the data prevents parallel changes to the same data, which would lead to data inconsistency. There is one instance of an enqueue service for each system - this instance becomes the central instance of the system by virtue of having this service. This Enqueue Client collects performance values for requests from other instances to this service. The Enqueue server provides the enqueue service for the system.

This test monitors the performance of the enqueue service.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Client_enqueue_freq The rate of Enqueue operations (logical data locks) coming from another instance to the central instance Locks/Min This is a relative measure of activity in the system, useful only for analyzing unusual events or patterns of activity in an application server. The R/3 enqueue service is capable of handling very high rates of operation. Should an alert occur, it indicates that the wait times for lock operations are having an adverse effect on the overall dialog response time. These situations are of a temporary nature and should correct themselves. They are likely to occur only under unusual circumstances, such as massively parallel execution of RFC calls to a particular server.
Server_queue_length The percentage length of the wait queue for the enqueue service Percent If an error occurs in this MTE, analyze the problem by executing the following diagnosis function in the lock management: Call Transaction SM12 and choose Extras -> Diagnosis or -> Diagnosis in update. With SAP'S agreement, you can use the extended diagnosis functions that are displayed by entering the OK codes “TEST”.
Owner_names Indicates the percentage of owner IDs in the lock table that are currently utilized. Percent Every time the enqueue server receives a lock request, the system checks the lock table to determine whether the request collides with an existing lock . If this is the case, the request is rejected. Otherwise, the new lock is written to the lock table. This lock table available in the main memory of the enqueue server records the current locks in the system.

For each elementary lock, the table specifies the owner, lock mode, name, and the fields in the locked table.

If the value of this measure is close to 100%, it indicates that all the owner IDs in the lock table are exhausted and hence, new locks cannot be created unless the existing locks assigned to the owner IDs are released.
Granule_args Indicates the percentage of lock arguments in the lock table that are currently utilized. Percent The locks of different owners or with different lock modes containing the same lock argument occupy one entry in the lock table.

If the value of this measure is close to 100%, it indicates that all the lock argument s in the lock table are exhausted and new locks cannot be created unless the existing locks are released.
Granule_entries Indicates the percentage of elementary locks in the lock table that are currently utilized. Percent An elementary lock corresponds to a data record in the lock table. For each elementary lock, the table specifies the owner, lock mode, name, and the fields in the locked table.

If the value of this measure is close to 100%. It indicates that all the elementary locks in the lock table are utilized and hence, new locks cannot be created unless the existing elementary locks are released from the lock table.
WP_errs Indicates the number of errors encountered by the enqueue work process. Number Ideally, the value of this measure should be zero.
WPErr_freq Indicates the rate of enqueue work process errors encountered. Errors/Min