HomeDataHPE NonStop SQL/MX Error – 30035 All rows in the NOT ATOMIC INSERT raised an error. No rows have been inserted.

HPE NonStop SQL/MX Error – 30035 All rows in the NOT ATOMIC INSERT raised an error. No rows have been inserted.

In this blog post, let’s learn about the error message “30035 All rows in the NOT ATOMIC INSERT raised an error. No rows have been inserted.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

30035 All rows in the NOT ATOMIC INSERT raised an error. No rows have been inserted.

Reason for the Error

All rows in the NOT ATOMIC inserts raised nonfatal errors.

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