How To Fix SBLM036 - Log2 limit set to &1 on server

SAP Error Message - Details

• Message type: E = Error

• Message class: SBLM - Blacklist Monitor: Message Classes

• Message number: 036

• Message text: Log2 limit set to &1 on server

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message SBLM036 - Log2 limit set to &1 on server ?

  The SAP error message SBLM036 indicates that the log file size limit for the server has been reached. This message typically appears in the context of SAP Business Suite applications, particularly when dealing with logging and monitoring functionalities.
  Cause:
  The error occurs when the log file size exceeds the predefined limit set for the server. This can happen due to:
  
  Excessive Logging: The application may be generating a large amount of log data due to high transaction volumes or verbose logging settings.
  Configuration Settings: The log file size limit may be set too low for the current usage patterns.
  Retention Policies: Old log files may not have been archived or deleted, leading to the accumulation of log data.
  
  Solution:
  To resolve the SBLM036 error, you can take the following steps:
  
  
  Increase Log File Size Limit:
  
  You can adjust the log file size limit in the server configuration settings. This is typically done in the SAP system configuration (transaction code RZ10 for profile parameters).
  Look for parameters related to logging, such as rdisp/log_size or similar, and increase the value.
  
  
  
  Manage Log Files:
  
  Regularly monitor and manage log files. Implement a log rotation or archiving strategy to ensure that old logs are removed or archived.
  Use transaction codes like SLG1 (Application Log) to review and delete unnecessary logs.
  
  
  
  Adjust Logging Levels:
  
  If the logging level is set to a verbose mode (e.g., debug), consider changing it to a less verbose level (e.g., info or warning) to reduce the amount of log data generated.
  
  
  
  Check for Errors:
  
  Investigate if there are any underlying issues causing excessive logging. This could be due to application errors or misconfigurations that need to be addressed.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or support notes for specific guidance related to your version of SAP and the logging framework in use.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 for viewing logs, RZ10 for profile parameters, and SM21 for system logs.
  SAP Notes: Check SAP Notes for any known issues or patches related to logging and the SBLM036 error.
  Performance Monitoring: Regularly monitor system performance and log file sizes to prevent future occurrences of this error.
  
  By following these steps, you should be able to resolve the SBLM036 error and manage log file sizes effectively in your SAP environment.