HomeDataHPE NonStop SQL/MX Error – 30028 NOT ATOMIC INSERT is not supported on a table that is the referencing table of referential integrity constraints. Referential integrity constraint constraint-name has table table-name as its referencing table.

HPE NonStop SQL/MX Error – 30028 NOT ATOMIC INSERT is not supported on a table that is the referencing table of referential integrity constraints. Referential integrity constraint constraint-name has table table-name as its referencing table.

In this blog post, let’s learn about the error message “30028 NOT ATOMIC INSERT is not supported on a table that is the referencing table of referential integrity constraints. Referential integrity constraint constraint-name has table table-name as its referencing table.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

30028 NOT ATOMIC INSERT is not supported on a table that is the referencing table of referential integrity constraints. Referential integrity constraint constraint-name has table table-name as its referencing table.

Reason for the Error

You attempted to use NOT ATOMIC inserts on a table that is the referencing table of referential integrity constraints.

Solution

Contact your service provider

Leave a Reply

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