HomeDataHPE NonStop SQL/MX Error – 6003 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value value for column name. If you have manually modified the metadata table, you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics.

HPE NonStop SQL/MX Error – 6003 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value value for column name. If you have manually modified the metadata table, you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics.

In this blog post, let’s learn about the error message “6003 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value value for column name. If you have manually modified the metadata table, you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

6003 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value value for column name. If you have manually modified the metadata table, you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics.

Reason for the Error

You have manually modified the metadata table, and now it contains an invalid boundary value.

Solution

Undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022