How To Fix DB6PM346 - Table &1 has a RUNSTATS profile, option to use profile is set

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 346

• Message text: Table &1 has a RUNSTATS profile, option to use profile is set

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 DB6PM346 - Table &1 has a RUNSTATS profile, option to use profile is set ?

  The SAP error message DB6PM346 indicates that a specific database table (denoted as &1) has a RUNSTATS profile associated with it, and the option to use this profile is currently enabled. This message typically arises in the context of database performance tuning and statistics management.
  Cause:
  The error occurs when the database system is trying to gather statistics for a table that has a RUNSTATS profile defined. The RUNSTATS profile specifies how statistics should be collected for that table, and if the option to use the profile is set, the system will adhere to the defined settings rather than using default or other methods for gathering statistics.
  Solution:
  To resolve this issue, you can consider the following steps:
  
  
  Check the RUNSTATS Profile: Review the RUNSTATS profile associated with the table to ensure that it is correctly configured. You may need to adjust the settings if they are not appropriate for your use case.
  
  
  Disable the Profile Option: If you do not want to use the RUNSTATS profile for this table, you can disable the option to use the profile. This can typically be done through the database management tools or SQL commands, depending on the database system you are using.
  
  
  Manually Gather Statistics: If necessary, you can manually gather statistics for the table without using the profile. This can be done using the appropriate SQL command for your database system (e.g., RUNSTATS command in DB2).
  
  
  Consult Documentation: Refer to the documentation for your specific database system to understand how RUNSTATS profiles work and how to manage them effectively.
  
  
  Database Administration: If you are unsure about making changes, consult with your database administrator (DBA) for guidance on how to proceed.
  
  
  Related Information:
  
  RUNSTATS Profiles: These profiles are used to define how and when statistics are collected for database objects. They can help optimize query performance by ensuring that the database has up-to-date statistics.
  Database Performance: Keeping statistics up to date is crucial for the query optimizer to make informed decisions about execution plans.
  SAP Notes: Check SAP Notes and Knowledge Base Articles for any specific recommendations or patches related to this error message.
  
  By following these steps, you should be able to address the DB6PM346 error and ensure that your database statistics are managed effectively.