How To Fix DB6129 - So far no table statistics have run without errors

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 129

• Message text: So far no table statistics have run without errors

Copy of DB6 126

What causes this issue?

Among other things, statistical information about tables (size,
distribution of values, and so on) is stored in the database system
tables (system catalog). The optimizer then analyzes this informaiton
when creating access plans for SQL statements.
For tables with variable datasets (transaction data), this statistical
information must be regularly adjusted.

System Response

The better these statistics, the better the optimizer can create plans.
Conversely, obsolete data or statistics that are missing completely can
cause poor access plans and therefore poor performance.

How to fix this error?

Maintain the table statistics with the help of the predefined actions
in the DB13 planning calendar. You can find more information about this
topic in the online documentation for the planning calendar. In the
special case of a BW system, there is a special report:
SAP_ANALYZE_ALL_INFOCUBES. This produces distributed statistics.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DB6129 - So far no table statistics have run without errors ?

  The SAP error message DB6129 indicates that there is an issue with the database statistics collection process. This error typically arises when the system attempts to gather statistics for database tables, but encounters errors that prevent the process from completing successfully. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Database Issues: There may be underlying issues with the database itself, such as corruption, locks, or configuration problems.
  Insufficient Permissions: The user or process attempting to collect statistics may not have the necessary permissions to access the tables or execute the required commands.
  Resource Limitations: The database server may be running low on resources (CPU, memory, disk space), which can lead to failures in executing statistics collection.
  Configuration Errors: Incorrect settings in the database or SAP system configuration can lead to failures in the statistics collection process.
  Inconsistent Data: If there are inconsistencies or issues with the data in the tables, this can also cause the statistics collection to fail.
  
  Solutions:
  
  Check Database Logs: Review the database logs for any specific error messages that can provide more context about why the statistics collection failed.
  Run Statistics Collection Manually: Attempt to run the statistics collection manually using the appropriate database commands or SAP transaction codes (e.g., DBACOCKPIT or ST03N).
  Check Permissions: Ensure that the user executing the statistics collection has the necessary permissions to access the tables and perform the required operations.
  Database Maintenance: Perform regular database maintenance tasks, such as reindexing or checking for corruption, to ensure the database is in good health.
  Resource Monitoring: Monitor the database server's resource usage to identify any bottlenecks or limitations that may be affecting performance.
  Configuration Review: Review the database and SAP configuration settings to ensure they are correctly set up for statistics collection.
  Consult Documentation: Refer to the SAP and database documentation for specific guidance on troubleshooting statistics collection issues.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to DB6129 for any specific patches or updates that may address the issue.
  Database Documentation: Consult the documentation for your specific database (e.g., Oracle, SQL Server, HANA) for best practices on statistics collection and troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your database administrator or SAP support for further assistance.