How To Fix /CDBASIS/MSG013 - Log size limit reached! No further messages will be logged.

SAP Error Message - Details

• Message type: E = Error

• Message class: /CDBASIS/MSG -

• Message number: 013

• Message text: Log size limit reached! No further messages will be logged.

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 /CDBASIS/MSG013 - Log size limit reached! No further messages will be logged. ?

  The SAP error message /CDBASIS/MSG013 Log size limit reached! No further messages will be logged. indicates that the log file for a specific application or process has reached its maximum size limit. This can prevent further logging of messages, which may hinder troubleshooting and monitoring activities.
  Cause:
  
  Log Size Limit Reached: The primary cause of this error is that the log file has reached its configured size limit. This can happen due to excessive logging or insufficient log rotation and management.
  Configuration Settings: The log size limit may be set too low for the volume of messages being generated by the application.
  Lack of Maintenance: If log files are not regularly archived or deleted, they can accumulate and reach their size limit.
  
  Solution:
  
  
  Increase Log Size Limit:
  
  You can increase the maximum size limit for the log file in the configuration settings. This can usually be done in the relevant configuration transaction (e.g., RZ10 for profile parameters).
  Look for parameters related to logging, such as log_file_size or similar, and adjust them accordingly.
  
  
  
  Log Rotation and Archiving:
  
  Implement a log rotation strategy to ensure that old logs are archived or deleted regularly. This can help manage log sizes effectively.
  You can set up a job to periodically archive logs or use tools provided by SAP for log management.
  
  
  
  Clear Existing Logs:
  
  If immediate action is required, you can manually clear or delete old log entries to free up space. Be cautious with this approach, as it may result in loss of important log data.
  Use transaction codes like SLG1 (Application Log) to view and manage logs.
  
  
  
  Monitor Logging:
  
  Regularly monitor the logging activity to ensure that it does not exceed the limits. This can help in identifying any unusual spikes in logging that may need to be addressed.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to logging and log management for specific guidance tailored to your SAP version and configuration.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SLG1: Display Application Log
  RZ10: Maintain Profile Parameters
  SM37: Monitor Job Logs
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to logging issues.
  Performance Considerations: Excessive logging can impact system performance, so it's essential to balance logging needs with system resources.
  
  By addressing the log size limit and implementing proper log management practices, you can prevent this error from occurring in the future and ensure that your logging system remains functional.