How To Fix RT867 - Percent of Available Physical CPUs Consumed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 867

• Message text: Percent of Available Physical CPUs Consumed

What causes this issue?

The percent of available physical CPU's consumed with respect to the
current available physical CPU's.

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 RT867 - Percent of Available Physical CPUs Consumed ?

  The SAP error message RT867, which indicates that the "Percent of Available Physical CPUs Consumed" has reached a critical threshold, typically arises in environments where SAP systems are running on virtualized infrastructure or where resource allocation is tightly monitored. This message is a warning that the system is consuming a high percentage of the available CPU resources, which can lead to performance degradation or system instability.
  Cause:
  
  High Workload: The SAP system may be experiencing a high volume of transactions or background jobs that require significant CPU resources.
  Inefficient Code: Custom ABAP programs or poorly optimized queries can lead to excessive CPU usage.
  Configuration Issues: Incorrect configuration of the SAP system or the underlying database can lead to inefficient resource utilization.
  Insufficient Hardware: The physical hardware may not be adequate to handle the workload, especially if the system has grown over time without corresponding hardware upgrades.
  Virtualization Overhead: In virtualized environments, the overhead of virtualization can sometimes lead to higher CPU consumption.
  
  Solution:
  
  
  Monitor and Analyze Workload:
  
  Use transaction codes like ST03N (Workload Analysis) and ST04 (Database Performance Analysis) to identify which processes are consuming the most CPU.
  Analyze the workload to determine if there are specific transactions or background jobs that are causing the spike.
  
  
  
  Optimize Code:
  
  Review and optimize any custom ABAP code or queries that are consuming excessive CPU resources.
  Consider using performance analysis tools like SAT (ABAP Trace) or ST05 (SQL Trace) to identify bottlenecks.
  
  
  
  Adjust Configuration:
  
  Review the configuration settings of the SAP system and the database to ensure they are optimized for performance.
  Check for any parameters that may need adjustment based on the current workload.
  
  
  
  Scale Resources:
  
  If the workload has increased significantly, consider scaling up the physical resources (adding more CPUs) or scaling out (adding more instances).
  In a virtualized environment, ensure that the virtual machine has been allocated sufficient CPU resources.
  
  
  
  Load Balancing:
  
  If applicable, implement load balancing to distribute the workload more evenly across available resources.
  
  
  
  Regular Maintenance:
  
  Schedule regular maintenance tasks to clean up old data, optimize database performance, and ensure that the system is running efficiently.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or patches related to performance issues.
  SAP Community: Engage with the SAP Community for insights and shared experiences from other users who may have faced similar issues.
  Performance Monitoring Tools: Consider using SAP Solution Manager or third-party monitoring tools to gain deeper insights into system performance and resource utilization.
  
  By addressing the underlying causes and implementing the suggested solutions, you can mitigate the RT867 error and improve the overall performance of your SAP system.