HPE NonStop SQL/MX Error – 1611 SET DEFAULT clause cannot be applied to column ColumnName which has a NO DEFAULT clause.

In this blog post, let’s learn about the error message “1611 SET DEFAULT clause cannot be applied to column ColumnName which has a NO DEFAULT clause.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1611 SET DEFAULT clause cannot be applied to column ColumnName which has a NO DEFAULT clause.

Reason for the Error

You attempted to create a referential integrity constraint with the SET DEFAULT clause for a column that was defined without a DEFAULT value.

Solution

Remove the SET DEFAULT clause in the referential integrity constraint or set a DEFAULT value for the column on which you want to create the referential integrity constraint

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