HPE NonStop SQL/MX Error – 4386 Update on primary key using blocking operator is not supported. Table affected-table is referenced by an incompatible RI constraint on table referencing-table.

In this blog post, let’s learn about the error message “4386 Update on primary key using blocking operator is not supported. Table affected-table is referenced by an incompatible RI constraint on table referencing-table.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

4386 Update on primary key using blocking operator is not supported. Table affected-table is referenced by an incompatible RI constraint on table referencing-table.

Reason for the Error

Update of a primary key column is not supported when that column is referenced by an RI constraint that uses the CASCADE, SET DEFAULT, or SET NULL referential action in combination with the ON UPDATE, or ON DELETE rule.

Solution

None. Use the SHOWDDL command to see the RI constraints which reference the affected-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