How To Fix DB6607 - Resetting old RUNSTATS check control table entries

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 607

• Message text: Resetting old RUNSTATS check control table entries

What causes this issue?

For database monitoring, the system fills various tables with temporary
data, which is regularly deleted or reset. This is a check control
table that contains the snapshot data for RUNSTATS. RUNSTATS is
executed for tables selected in DBSTATC.

System Response

This monitor attribute is for informational purposes.

How to fix this error?

If there is an error, use transaction RZ20 to analyse the cause of the
error (monitor set <LS>CCMS Monitor Templates</> -> <LS>Database</>
monitor.

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 DB6607 - Resetting old RUNSTATS check control table entries ?

  The SAP error message DB6607, which states "Resetting old RUNSTATS check control table entries," typically relates to issues with the database statistics collection process in SAP systems. This message is often associated with the database management system (DBMS) that SAP is using, such as Oracle, DB2, or others.
  Cause:
  The error message DB6607 indicates that the system has detected old entries in the RUNSTATS check control table. This can happen due to various reasons, including:
  
  Outdated Statistics: The database statistics may not have been updated for a long time, leading to stale entries.
  Database Configuration Issues: There may be configuration issues in the database that prevent the RUNSTATS process from executing correctly.
  Job Failures: If the scheduled jobs for collecting statistics have failed or been interrupted, it can lead to old entries remaining in the control table.
  Database Maintenance: Regular maintenance tasks may not have been performed, leading to inconsistencies in the statistics.
  
  Solution:
  To resolve the DB6607 error, you can take the following steps:
  
  
  Run Statistics Collection: Manually trigger the RUNSTATS process to update the statistics for the database objects. This can often be done through the SAP transaction code DBACOCKPIT or through the database's native tools.
  
  
  Check Job Logs: Review the logs of the jobs responsible for collecting statistics to identify any failures or issues. This can help you understand why the statistics were not updated.
  
  
  Database Configuration: Ensure that the database is properly configured for statistics collection. Check the settings related to automatic statistics gathering and ensure they are enabled.
  
  
  Clean Up Old Entries: If necessary, you may need to manually clean up old entries in the RUNSTATS check control table. This should be done with caution and ideally under the guidance of a database administrator.
  
  
  Schedule Regular Maintenance: Set up a regular schedule for running statistics collection to prevent the issue from recurring in the future.
  
  
  Consult Documentation: Refer to the SAP Notes and documentation specific to your database system for any additional steps or recommendations.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to database statistics and the specific error message for any patches or updates that may address the issue.
  Database Documentation: Review the documentation for your specific database system (e.g., Oracle, DB2) for best practices on managing statistics.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  By following these steps, you should be able to address the DB6607 error and ensure that your database statistics are up to date.