Do you have any question about this error?
Message type: E = Error
Message class: /SDF/MON -
Message number: 036
Message text: Monitoring the CPU times may cause high system CPU load
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
The SAP error message
/SDF/MON036
indicates that monitoring CPU times may lead to high system CPU load. This message is typically related to the SAP Solution Manager and its monitoring capabilities, particularly when it is configured to track CPU usage metrics.Cause:
- High Monitoring Frequency: The monitoring process may be set to a very frequent interval, which can lead to increased CPU usage as the system continuously collects and processes monitoring data.
- Resource-Intensive Monitoring: The specific monitoring tasks or metrics being tracked may be resource-intensive, causing additional load on the CPU.
- System Configuration: The configuration of the monitoring tools may not be optimized for the current system load or hardware capabilities.
- Background Jobs: If there are many background jobs running simultaneously, the additional monitoring load can exacerbate CPU usage.
Solution:
- Adjust Monitoring Frequency: Review and adjust the frequency of the monitoring tasks. Increasing the interval between monitoring checks can help reduce CPU load.
- Optimize Monitoring Settings: Disable or limit the monitoring of less critical metrics that may not be necessary for your operations.
- Review System Resources: Ensure that the system has adequate resources (CPU, memory) to handle the monitoring tasks. If necessary, consider upgrading hardware.
- Analyze Background Jobs: Check for any unnecessary background jobs that may be running and consuming CPU resources. Optimize or schedule them during off-peak hours.
- Use Performance Analysis Tools: Utilize SAP's performance analysis tools to identify bottlenecks and optimize the overall system performance.
- Consult SAP Notes: Check for any relevant SAP Notes or updates that may address known issues related to monitoring and CPU load.
Related Information:
If the problem persists after implementing these solutions, it may be beneficial to engage SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
/SDF/MON035 Monitoring the outbound queue may cause a high workload
Self-Explanatory Message Since SAP believes that this specific error message is ...
/SDF/MON034 Monitoring the inbound queue may cause a high workload
Self-Explanatory Message Since SAP believes that this specific error message is ...
/SDF/MON037 Multiple Selection not possible for this function
Self-Explanatory Message Since SAP believes that this specific error message is ...
/SDF/MON038 Start time after end time
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.