How To Fix RT749 - Enqueue statistics - for more information, see long text

SAP Error Message - Details

• Message type: E = Error

• Message class: RT - Monitoring infrastructure MSG and alert texts

• Message number: 749

• Message text: Enqueue statistics - for more information, see long text

What causes this issue?

Enqueue Requests
Number of lock requests
Enqueue Request Rejects
Number of rejected lock requests
Enqueue Request Errors
Number of errors that occurred during lock requests
Dequeue Requests
Release requests ( DEQUEUE )
Dequeue Request Errors
Number of errors that occurred when releasing locks
DequeueAll Requests
Release of all locks for a LUW, for example at the end of a LUW
CleanUp Requests
Number of releases of all locks for an application server, for example
at shutdown or startup
Backup Requests
Number of update calls at which locks are forwarded to the update task.
The scope-2 lock owner ID of the caller is passed to the update task and
the caller receives a new scope-2 lock owner ID.
Reporting Requests
Number of operations to read the lock table
Owner Names
Maximum number of lock owner IDs that the lock table can include. Lock
owner IDs are assigned to a user context or an update request.
Owner Names Peak Utilization
Maximum number of lock owners that have been in the lock table
concurrently up to now
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
include. Locks with different lock owners or different lock modes, but
the same lock argument occupy one entry.
Granule Arguments Peak Utilization
Highest number of different lock arguments that have been in the lock
table concurrently so far
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 include. Each
elementary lock occupies one entry.
Granule Entries Peak Utilization
Highest number of elementary locks that have been in the lock table
concurrently so far
Granule Entries Actual Utilization
Current number of elementary locks in the lock table
Update Queue Peak
Maximum number of open update requests with locks so far
Update Queue Actual
Current number of open update requests with locks
Total Lock Time
Total time used for lock operations in the critical path of the lock
table
Recent Lock Time (per minute)
Time used for lock operations in the critical path of the lock table in
seconds / 1 minute.
Total Lock Wait Time
Total wait time of parallel processes before entry into the critical
path of the lock table
Recent Lock Wait Time (per minute)
Wait time of parallel processes before entry into the critical path of
the lock table in seconds / 1 minute
Total Server Time
Total time spent on the lock server-side
Recent Server Time (per minute)
Total time spent on the lock server-side in seconds / 1 minute
Runtime of Data Collector
Node to which the data collection method is assigned. The runtime of
each data collection is monitored using this node.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RT749 - Enqueue statistics - for more information, see long text ?

  The SAP error message RT749 typically relates to issues with enqueue statistics in the SAP system. This error can occur when there are problems with the enqueue server, which is responsible for managing locks on objects in the SAP system to ensure data consistency.
  Cause:
  
  Lock Table Issues: The enqueue server may be experiencing issues with the lock table, such as being full or having inconsistencies.
  Performance Problems: High load on the enqueue server can lead to performance degradation, causing delays in processing lock requests.
  Configuration Issues: Incorrect configuration settings for the enqueue server or the SAP system can lead to this error.
  Network Issues: Problems with network connectivity between application servers and the enqueue server can also trigger this error.
  
  Solution:
  
  Check Enqueue Server Status: Use transaction code SM12 to check for any locks that may be causing issues. You can also check the status of the enqueue server using transaction SM66 or SM50.
  Monitor Performance: Use transaction ST02 to monitor memory and performance statistics. Look for any bottlenecks or high resource usage.
  Review Configuration: Ensure that the configuration settings for the enqueue server are correct. This includes checking parameters in the instance profile related to the enqueue server.
  Restart Enqueue Server: If the issue persists, consider restarting the enqueue server. This can help clear any temporary issues affecting its performance.
  Check System Logs: Use transaction SM21 to review system logs for any related error messages or warnings that could provide more context on the issue.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (Lock Entries), SM21 (System Log), SM66 (Global Work Process Overview), and ST02 (Tune Summary).
  SAP Documentation: Refer to the official SAP documentation for detailed information on enqueue management and troubleshooting.
  SAP Community: Engage with the SAP Community forums for insights and solutions shared by other SAP users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.