HPE NonStop SQL/MX Error – 1614 Constraint constraintName could not be created as referencing column columnName is part of clustering key of table tableName.

In this blog post, let’s learn about the error message “1614 Constraint constraintName could not be created as referencing column columnName is part of clustering key of table tableName.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1614 Constraint constraintName could not be created as referencing column columnName is part of clustering key of table tableName.

Reason for the Error

You attempted to create a referential integrity constraint with a referencing column that is a part of the clustering key of the referencing table.

Solution

None

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