HPE NonStop SQL/MX Error – 1598 The new CURRENT_VALUE, current-value,for the IDENTITY column, col-name, for the table, table-name, will be greater than the allowed, maximum-value.

In this blog post, let’s learn about the error message “1598 The new CURRENT_VALUE, current-value,for the IDENTITY column, col-name, for the table, table-name, will be greater than the allowed, maximum-value.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1598 The new CURRENT_VALUE, current-value,for the IDENTITY column, col-name, for the table, table-name, will be greater than the allowed, maximum-value.

Reason for the Error

The new CURRENT_VALUE is greater than the maximum value allowed for the IDENTITY column data type or is greater than the MAXVALUE option. The CURRENT_VALUE is calculated by adding INCREMENT BY option value to the base current value.

Solution

Determine if changing the options of the IDENTITY column results in calculation of a valid new CURRENT_VALUE maximum. If a new maximum does exist, alter the options using ALTER TABLE ALTER COLUMN SET command, and resubmit the RECALIBRATE command

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