How To Fix DB6PM767 - DBCFG - NUM_QUANTILES: Execute RUNSTATS command after changing the value

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring

• Message number: 767

• Message text: DBCFG - NUM_QUANTILES: Execute RUNSTATS command after changing the value

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 DB6PM767 - DBCFG - NUM_QUANTILES: Execute RUNSTATS command after changing the value ?

  The SAP error message DB6PM767 DBCFG - NUM_QUANTILES: Execute RUNSTATS command after changing the value typically indicates that there has been a change in the database configuration related to the NUM_QUANTILES parameter, which affects how the database collects statistics for query optimization.
  Cause:
  
  Parameter Change: The NUM_QUANTILES parameter controls the number of quantiles that the database collects for statistics. If this value is changed, the database needs to recalculate the statistics to reflect the new configuration.
  Outdated Statistics: The existing statistics may not be valid anymore due to the change in the NUM_QUANTILES setting, which can lead to suboptimal query performance.
  
  Solution:
  To resolve this error, you need to execute the RUNSTATS command. This command collects and updates the statistics for the database objects (tables, indexes, etc.) based on the new configuration. Here’s how you can do it:
  
  Connect to the Database: Use a database client or command line to connect to your database.
  Execute RUNSTATS: Run the following command:
  RUNSTATS ON TABLE <schema_name>.<table_name>;
  Replace <schema_name> and <table_name> with the appropriate schema and table names. If you want to update statistics for all tables, you may need to run the command for each table or use a script to automate it.
  
  Verify Execution: After executing the command, check for any errors and ensure that the statistics have been updated successfully.
  
  Related Information:
  
  Documentation: Refer to the database documentation for specific details on the RUNSTATS command and its options.
  Performance Monitoring: After updating the statistics, monitor the performance of your queries to ensure that they are optimized based on the new statistics.
  Regular Maintenance: It is a good practice to regularly update statistics, especially after significant changes to the data or configuration settings.
  
  Additional Considerations:
  
  Database Version: The exact syntax and options for the RUNSTATS command may vary depending on the database version you are using (e.g., DB2, HANA, etc.).
  Automated Jobs: Consider setting up automated jobs to run RUNSTATS periodically or after significant changes to the database to maintain optimal performance.
  
  By following these steps, you should be able to resolve the error and ensure that your database is functioning optimally with the new configuration settings.