HPE NonStop SQL/MX Error – 1072 Unique constraint constraint-name-1 is disabled, so foreign key constraint constraint-name-2 could not be created.

In this blog post, let’s learn about the error message “1072 Unique constraint constraint-name-1 is disabled, so foreign key constraint constraint-name-2 could not be created.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1072 Unique constraint constraint-name-1 is disabled, so foreign key constraint constraint-name-2 could not be created.

Reason for the Error

You created a referential constraint that references a unique constraint that has been disabled. This is an internal error.

Solution

Create the referential constraint that references a unique constraint that has not been disabled

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