How To Fix AD921 - Log older than & was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: AD - Data Dictionary application messages

• Message number: 921

• Message text: Log older than & was not found

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 AD921 - Log older than & was not found ?

  The SAP error message AD921 indicates that a log file that is older than a specified time frame was not found. This error typically occurs in the context of the SAP system's application log or when dealing with background jobs, particularly when the system is trying to access logs that have been archived or deleted.
  Cause:
  
  Log Retention Policy: The system may have a log retention policy that automatically deletes logs older than a certain age. If the log you are trying to access exceeds this age, it may no longer be available.
  Archiving: Logs may have been archived to save space, and the system is unable to find the log in the active log storage.
  Incorrect Log ID: The log ID or reference being used to access the log may be incorrect or may not exist in the system.
  System Configuration: There may be configuration settings that dictate how long logs are retained, and these settings may not align with your expectations.
  
  Solution:
  
  Check Log Retention Settings: Review the log retention settings in your SAP system. You can do this by checking the configuration in transaction codes like SARA (Archive Administration) or SLG1 (Application Log).
  Access Archived Logs: If the logs have been archived, you may need to access them through the archiving process. Use transaction SARA to check if the logs are archived and how to retrieve them.
  Verify Log ID: Ensure that the log ID or reference you are using is correct. You can check the logs using transaction SLG1 to see if the log exists.
  Adjust Retention Policy: If necessary, adjust the retention policy to keep logs for a longer period, but be mindful of the storage implications.
  Consult Documentation: Refer to SAP documentation or support notes related to application logs and log management for more detailed guidance.
  
  Related Information:
  
  Transaction Codes:
  
  SLG1: Display Application Log
  SARA: Archive Administration
  SLG2: Display Application Log (for specific objects)
  
  
  SAP Notes: Check SAP Notes for any known issues or updates related to log management and the AD921 error.
  System Monitoring: Regularly monitor your system's log management settings to ensure they align with your operational needs.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis team or SAP support for further assistance.