How To Fix DB6604 - Old entries have not been deleted

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 604

• Message text: Old entries have not been deleted

Copied from DB6 602

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 DB6604 - Old entries have not been deleted ?

  The SAP error message DB6604 "Old entries have not been deleted" typically occurs in the context of database management, particularly when dealing with database table entries that are supposed to be deleted but have not been successfully removed. This can happen for various reasons, including database locks, constraints, or issues with the deletion process itself.
  Causes:
  
  Database Locks: If another process is holding a lock on the entries that need to be deleted, the deletion operation may fail.
  Foreign Key Constraints: If there are foreign key constraints that prevent the deletion of certain entries, the system will not allow the deletion to proceed.
  Insufficient Authorizations: The user executing the deletion may not have the necessary authorizations to delete the entries.
  Database Corruption: In rare cases, database corruption can lead to issues with deleting entries.
  Batch Job Failures: If the deletion is part of a batch job, any failure in the job can lead to incomplete deletions.
  
  Solutions:
  
  Check Locks: Use transaction codes like SM12 to check for any locks on the database entries. If locks are found, you may need to wait for the locking process to complete or resolve the lock manually.
  Review Foreign Key Constraints: Check the database schema for any foreign key constraints that might be preventing the deletion. You may need to delete dependent entries first.
  Verify Authorizations: Ensure that the user has the necessary authorizations to perform deletion operations on the relevant tables.
  Run Consistency Checks: Use transaction codes like DB02 or DBACOCKPIT to check for database consistency and integrity. If corruption is suspected, you may need to restore from a backup.
  Check Batch Job Logs: If the deletion is part of a batch job, review the job logs for any errors or warnings that could indicate why the deletion did not complete successfully.
  Manual Deletion: If automated processes fail, consider manually deleting the entries using SQL commands or through the SAP GUI, ensuring that you follow the necessary procedures to maintain data integrity.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE14 (Database Utility), and SM37 (Job Monitoring) for troubleshooting.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Database Administration: If you have access to database administration tools, you may want to consult with your database administrator for deeper insights into the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with SAP support or your internal IT team for further assistance.