How To Fix DB6602 - Deletion of old entries in the alert message log

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6 - DB6: Alert Monitoring and Alert Configuration

• Message number: 602

• Message text: Deletion of old entries in the alert message log

What causes this issue?

For data monitoring, the system temporarily fills a table that logs
alerts. The system regularly deletes or resets this data.

System Response

If automatic deletion does not work, space is unnecessarily used.

How to fix this error?

If this is the case, delete the entries manually using transaction
DB37.

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DB6602 - Deletion of old entries in the alert message log ?

  The SAP error message DB6602 typically indicates an issue related to the deletion of old entries in the alert message log. This log is used to track alerts and messages generated by the SAP system, and it can grow over time, potentially leading to performance issues or storage concerns.
  Cause:
  The error message DB6602 can occur due to several reasons, including:
  
  Database Constraints: There may be constraints or locks on the database that prevent the deletion of old entries.
  Insufficient Authorizations: The user executing the deletion may not have the necessary authorizations to perform this action.
  System Configuration: The system may not be configured correctly to allow for the automatic deletion of old log entries.
  Database Size Limitations: The database may have reached its size limit, preventing further entries from being logged or old entries from being deleted.
  
  Solution:
  To resolve the DB6602 error, you can take the following steps:
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to delete entries from the alert message log. You may need to consult with your SAP security team to verify this.
  
  
  Review Database Locks: Check for any locks or constraints on the database that may be preventing the deletion of entries. You can use transaction codes like SM12 (to check for locks) and SM21 (to review system logs) to investigate.
  
  
  Adjust System Configuration: Review the configuration settings related to the alert message log. You may need to adjust parameters in transaction codes like RZ10 (for profile parameters) or RZ20 (for monitoring).
  
  
  Manual Deletion: If automatic deletion is not working, you may need to manually delete old entries from the alert message log. This can typically be done through transaction codes like SLG1 (for application log) or using specific database commands if you have the necessary access.
  
  
  Database Maintenance: Perform regular database maintenance to ensure that the database is optimized and that old entries are being purged as expected. This may include running database cleanup jobs or archiving old data.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates available that can resolve the issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SM12 (Lock Entries), and SM21 (System Log) for troubleshooting.
  SAP Documentation: Review SAP documentation related to alert message logs and database management for best practices and guidelines.
  SAP Community: Engage with the SAP Community forums for insights and solutions shared by other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.