How To Fix GT920 - Logs older than & were deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: GT - Database utilities

• Message number: 920

• Message text: Logs older than & were deleted

What causes this issue?

All logs older than the date specified were deleted.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

No action required.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GT920 - Logs older than & were deleted ?

  The SAP error message GT920 indicates that logs older than a specified retention period have been deleted. This message typically arises in the context of the SAP system's log management, particularly when dealing with application logs, system logs, or other types of logs that are subject to retention policies.
  Cause:
  
  Log Retention Policy: SAP systems have a configured retention policy that determines how long logs are kept. When logs exceed this retention period, they are automatically deleted to free up space and maintain system performance.
  Manual Deletion: Logs may also be deleted manually by an administrator or through a scheduled job that cleans up old logs.
  System Configuration: The system may be configured to delete logs based on certain criteria, such as age or size.
  
  Solution:
  
  Check Log Retention Settings: Review the log retention settings in your SAP system. You can do this by navigating to the relevant configuration settings in transaction codes like SARA (Archive Administration) or SLG1 (Application Log).
  Adjust Retention Period: If necessary, adjust the retention period to keep logs for a longer duration. This can be done in the configuration settings where you define how long logs should be retained.
  Review Deletion Jobs: Check if there are any scheduled jobs that are set to delete logs. You can do this in transaction SM37 (Job Monitoring) to see if any jobs are running that might be causing the deletion.
  Log Retrieval: If you need to access logs that have already been deleted, consider implementing an archiving strategy that allows you to archive logs before they are deleted, ensuring that you can retrieve them if needed.
  Monitoring: Set up monitoring to alert you when logs are nearing their retention limits, so you can take action before they are deleted.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SLG1: Display Application Log
  SARA: Archive Administration
  SM37: Job Monitoring
  
  
  SAP Notes: Check SAP Notes for any specific guidance or updates related to log management and retention policies.
  Documentation: Review SAP documentation regarding log management and archiving to understand best practices and configurations.
  
  By following these steps, you can manage log retention effectively and avoid unexpected deletions that may impact your operations.