How To Fix DB02060 - Maintenance of CBO (cost-based optimizer) statistics

SAP Error Message - Details

• Message type: E = Error

• Message class: DB02 - For Oracle Component of the Database Monitor

• Message number: 060

• Message text: Maintenance of CBO (cost-based optimizer) statistics

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message DB02060 - Maintenance of CBO (cost-based optimizer) statistics ?

  The SAP error message DB02060 typically relates to issues with the maintenance of Cost-Based Optimizer (CBO) statistics in the database. This error can occur in various database systems that SAP supports, such as Oracle, SQL Server, or others. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Outdated Statistics: The CBO relies on accurate statistics to generate optimal execution plans. If the statistics are outdated or missing, it can lead to suboptimal performance and errors.
  Database Configuration: Certain database configurations may prevent the automatic gathering of statistics.
  Insufficient Privileges: The user executing the statistics maintenance may not have the necessary privileges to gather or update statistics.
  Database Corruption: In rare cases, database corruption can lead to issues with statistics maintenance.
  
  Solution:
  
  
  Gather Statistics:
  
  Use the appropriate command for your database to gather statistics. For example, in Oracle, you can use:
  EXEC DBMS_STATS.GATHER_SCHEMA_STATS('YOUR_SCHEMA_NAME');
  
  In SQL Server, you can use:
  EXEC sp_updatestats;
  
  
  
  
  Check Automatic Statistics Gathering:
  
  Ensure that automatic statistics gathering is enabled in your database configuration. For Oracle, you can check the AUTO_STATS_TARGET parameter.
  
  
  
  Review User Privileges:
  
  Ensure that the user executing the statistics maintenance has the necessary privileges. This may include roles like DBA or specific privileges to gather statistics.
  
  
  
  Database Health Check:
  
  Perform a health check on the database to ensure there are no underlying issues. This may include checking for corruption or other anomalies.
  
  
  
  Schedule Regular Maintenance:
  
  Implement a regular maintenance schedule for gathering statistics to prevent this issue from recurring.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to DB02060 for specific guidance or patches that may address the issue.
  Database Documentation: Refer to the documentation for your specific database system for best practices on maintaining statistics.
  Performance Monitoring: Use performance monitoring tools to analyze query performance and identify if outdated statistics are affecting execution plans.
  
  Conclusion:
  Addressing the DB02060 error involves ensuring that CBO statistics are up-to-date and that the database is configured correctly for maintenance tasks. Regular monitoring and maintenance can help prevent this error from occurring in the future. If the problem persists, consider reaching out to SAP support or your database administrator for further assistance.