The enqueue service allows ABAP applications to lock data so that only they can use it. The locking of the data avoids parallel changes to the data, which would lead to data inconsistency. For more information, see 
The SAP Lock Concept (BC-CST-EQ).
There are two different trees in the monitoring infrastructure for monitoring the enqueue service:
· Enqueue monitor in the SAP CCMS Monitor Templates monitor set
This monitor includes a large number (see below) of monitoring values for the enqueue service. Since the monitor is supplied with values by an ABAP data collection method, the values are updated every five minutes.
· Enqueue subtree in the R3Services subtree of the Entire System Monitor (SAP CCMS Monitor Templates monitor set)
This subtree includes only the most important monitoring values for the enqueue service. Since the data is supplied by an active data supplier directly from the kernel, current data is reported immediately in the monitoring infrastructure.
Enqueue Monitor
Features
The monitor contains the following monitoring tree elements (MTEs):
MTE Name | Meaning |
Enqueue Server | Enqueue server that provides the enqueue service for the system |
Enqueue Requests | Number of lock requests |
Enqueue Request Rejects | Number of rejected lock requests |
Enqueue Requests Errors | Number of errors that occurred during lock requests |
Dequeue Requests | Number of release requests (DEQUEUE)( |
Dequeue Requests Errors | Number of errors that occurred when releasing locks |
DequeueAll Requests | Number of releases of all locks of an LUW (such as at the end of an LUW) |
CleanUp Requests | Number of releases of all locks of an application server (such as when the server is started or shut down) |
Backup Requests | Number of update calls for which locks were forwarded to the update. The update process receives the lock owner ID of the caller, the caller receives a new lock owner ID. |
Reporting Requests | Number of operations for reading the lock table. |
Owner Names | Maximum number of lock owner IDs that can be stored in the lock table. Lock owner IDs are assigned to a user context or to an update request. |
Owner Names Peak Utilization | Maximum number of lock owners that have been stored simultaneously in the lock table. |
Owner Names Actual Utilization | Current number of lock owners in the lock table |
Granule Arguments | Maximum number of different lock arguments that the lock table can contain; locks of different owners or with different lock modes, but with the same lock argument occupy one entry |
Granule Arguments Peak Utilization | Maximum number of different lock arguments that have been stored simultaneously in the lock table. |
Granule Arguments Actual Utilization | Current number of different lock arguments in the lock table |
Granule Entries | Maximum number of elementary locks that the lock table can contain (each elementary lock occupies one entry) |
Granule Entries Peak Utilization | Maximum number of elementary locks that have been stored simultaneously in the lock table. |
Granule Entries Actual Utilization | Current number of elementary locks in the lock table |
Update Queue Peak | Maximum number of open update requests with locks that has occurred so far |
Update Queue Actual | Current number of open update requests with locks |
Total Lock Time | Total time spent in the critical path of the lock table for lock operations |
Recent Lock Time (per minute) | Time spent in the critical path of the lock table for lock operations (in seconds per minute) |
Total Lock Wait Time | Total wait time of parallel processes before entering the critical path of the lock table |
Recent Lock Wait Time (per minute) | Wait time of parallel processes before entering the critical path of the lock table (in seconds per minute) |
Total Server Time | Total time spent in the enqueue server |
Recent Server Time (per minute) | Total time spent in the enqueue server (in seconds per minute) |
Runtime of Data Collector | Node that is assigned to the data collection method; this is used to monitor the runtime of each data collection |
Enqueue Clients | There is one instance with an enqueue service for each system ‑ this instance becomes the central instance of the system because it has this service. This monitoring object contains performance attributes for requests from the other instances to this service. |
| Instance name |
EnqueueFreq | Enqueue operations (logical data locks) per minutes that are coming from another instance to the central instance |
Connection to Standalone Enqueue | If the system contains a |
| Instance name |
Description | Version of the standalone enqueue server |
Status | Status of the connection of the instance to the standalone enqueue server |
ReplicationStatus | Together with an enqueue replication server, the standalone enqueue server forms a high-availability enqueue server. If a replication server is installed, its current status is displayed here. |
ReplicaAvailability | Availability of the replication server. If the server is not installed, the node contains the value 0%. |
Log | Messages of the standalone enqueue server |
Activities
To start the monitor, follow the procedure below:
...
1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.
2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
3. Start the Enqueue Server monitor from the list by double-clicking it.
Enqueue Subtree in R3Services
Features
The subtree contains the following MTEs:
MTE Name | Meaning |
Enqueue | Enqueue service subtree |
EnqueueClient | Subtree for the enqueue client; this exists on every instance |
EnqueueFreq | Enqueue operations (logical data locks) per minutes that are coming from another instance to the central instance |
EnqueueServer | Subtree for the enqueue client; this only exists on the central instance |
QueueLength | Length of the enqueue queue as a percentage of its maximum length |
ErrorsInWpENQ | Number of errors in the enqueue work processes since the monitoring segment was created (that is, since the application server was started) |
ErrorFreqInWpENQ | Number of errors in the enqueue work processes per minute |
EndedWpENQ | Number of enqueue work processes terminated after an error; you can use the Process Overview (transaction SM50) to determine whether a work process should be restarted after an error |
Utilization Owner Names | Current number of lock owners in the lock table as a percentage of the maximum number |
Utilization Granule Arguments | Current number of different lock arguments in the lock table as a percentage of the maximum number |
Utilization Granule Entries | Current number of elementary locks in the lock table as a percentage of the maximum number |
Activities
To display the subtree, proceed as follows:
...
1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.
2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
3. Start the Entire System monitor from the list by double-clicking it, and expand the monitoring tree along the path
No comments:
Post a Comment