HPE NonStop SQL/MX Error – 1622 INCREMENT BY value is inconsistent with MAXVALUE and MINVALUE settings for seq-name.

In this blog post, let’s learn about the error message “1622 INCREMENT BY value is inconsistent with MAXVALUE and MINVALUE settings for seq-name.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1622 INCREMENT BY value is inconsistent with MAXVALUE and MINVALUE settings for seq-name.

Reason for the Error

The combination of INCREMENT BY, MINVALUE, and MAXVALUE settings results in the sequence generator generating only a single value per cycle.

Solution

Specify INCREMENT BY, MINVALUE, and MAXVALUE settings so that the sequence generator can generate at least two values per cycle

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