HPE NonStop SQL/MX Error – 1302 NO ACTION referential action for referential-triggered-action clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.

In this blog post, let’s learn about the error message “1302 NO ACTION referential action for referential-triggered-action clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1302 NO ACTION referential action for referential-triggered-action clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.

Reason for the Error

NO ACTION referential action is specified in the referential definition and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is ‘SYSTEM.’

Solution

To alter the behavior of the NO ACTION referential action, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default

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