HPE NonStop SQL/MX Error – QL 20792079 string1 should always be less than or equal to CQD string2. Value of string2 is value1 and value of string1 is value2.

In this blog post, let’s learn about the error message “QL 20792079 string1 should always be less than or equal to CQD string2. Value of string2 is value1 and value of string1 is value2.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

QL 20792079 string1 should always be less than or equal to CQD string2. Value of string2 is value1 and value of string1 is value2.

Reason for the Error

You attempted to set the value of default attribute NUMERIC_PARAM_DEFAULT_SCALE to greater than the current value of default attribute NUMERIC_PARAM_DEFAULT_PRECISION. Or, you attempted to set the value of default attribute NUMERIC_PARAM_DEFAULT_PRECISION to less than the current value of default attribute NUMERIC_PARAM_DEFAULT_SCALE.

Or

You attempted to set the value of default attribute NUMBER_DEFAULT_SCALE to greater than the current value of default attribute NUMBER_DEFAULT_PRECISION. Or, you attempted to set the value of default attribute NUMBER_DEFAULT_PRECISION to less than the current value of default attribute NUMBER_DEFAULT_SCALE.

Solution

Ensure the value of default attribute NUMERIC_PARAM_DEFAULT_SCALE is less than or equal to the value of default attribute NUMERIC_PARAM_DEFAULT_PRECISION. Value of default attribute NUMERIC_PARAM_DEFAULT_PRECISION should be changed suitably to adjust changes to the attribute NUMERIC_PARAM_DEFAULT_SCALE. Any change in either of these default attributes might effect the plans.

Or

Ensure the value of default attribute NUMBER_DEFAULT_SCALE is less than or equal to the value of default attribute NUMBER_DEFAULT_PRECISION. Value of default attribute NUMBER_DEFAULT_PRECISION should be changed suitably to adjust changes to the attribute NUMBER_DEFAULT_SCALE. Any change in either of these default attributes might effect the plans

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