How To Fix RT642 - Number of jobs that are waiting for execution (cross-system average)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 642

• Message text: Number of jobs that are waiting for execution (cross-system average)

What causes this issue?

Number of execution-ready jobs with start authorization for which there
are no free background work processes, averaged across all background
servers.
The sytem-wide length of the wait queue provides a central overview
statistic for background processing in your system. Even if, for
example, problems occur in one background server, the low system-wide
length of the wait queue indicates that this is only a local problem on
that server.

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?

If alerts are repeatedly raised in this node, you should increase the
background processing capacity:
Set the number of work processes for background processing for each
application server with the system parameter <LS>rdisp/wp_no_btc
</>.
For more information about this topic, see SAP Note 39412 (How many
work processes to configure).

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 RT642 - Number of jobs that are waiting for execution (cross-system average) ?

  The SAP error message RT642 indicates that the number of jobs waiting for execution has exceeded the defined threshold in the system. This can occur in a variety of scenarios, particularly in environments with high job scheduling and processing demands.
  Cause:
  
  High Job Volume: A large number of background jobs are scheduled, leading to a backlog.
  System Resource Constraints: Insufficient system resources (CPU, memory, etc.) can slow down job processing.
  Configuration Issues: The system may not be optimally configured for job processing, including settings related to job scheduling and execution.
  Long-Running Jobs: Some jobs may be taking longer than expected to complete, causing a queue to build up.
  Deadlocks or Locks: Jobs may be waiting for resources that are locked by other processes.
  
  Solution:
  
  Monitor Job Status: Use transaction codes like SM37 to monitor the status of background jobs. Identify any jobs that are stuck or taking too long to complete.
  Analyze Job Logs: Check the logs of long-running jobs for errors or issues that may be causing delays.
  Increase Resources: If the system is under heavy load, consider increasing the hardware resources (CPU, memory) or optimizing the existing resources.
  Adjust Job Scheduling: Review the scheduling of jobs to ensure they are not all set to run at the same time. Staggering job execution can help manage load.
  Optimize Long-Running Jobs: Review and optimize the code or logic of jobs that consistently take a long time to execute.
  Check for Locks: Use transaction SM12 to check for locks that may be causing jobs to wait. Resolve any unnecessary locks.
  System Configuration: Review and adjust the configuration settings related to background processing in transaction RZ10 or RZ11 to ensure they are appropriate for your workload.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to job scheduling and performance issues for specific guidance and patches.
  Performance Monitoring: Utilize tools like SAP Solution Manager or transaction ST03N to monitor system performance and identify bottlenecks.
  Background Processing Configuration: Review the background processing configuration in transaction SM36 to ensure it aligns with your system's needs.
  Job Prioritization: Consider prioritizing critical jobs to ensure they are processed in a timely manner.
  
  By addressing the underlying causes and implementing the suggested solutions, you can mitigate the RT642 error and improve the efficiency of job processing in your SAP system.