HPE NonStop SQL/MX Error – 1005 Constraint constraint-name does not exist.

In this blog post, let’s learn about the error message “1005 Constraint constraint-name does not exist.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1005 Constraint constraint-name does not exist.

Reason for the Error

The ALTER TABLE statement you attempted requires the existence of a constraint named constraint-name.

Solution

Check that a constraint named constraint-name exists for the table specified. You can use the SHOWDDL command to find the names of the constraints that exist on a table

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