HPE NonStop SQL/MX Error – 20724 Audit fixup process process name found a violation of the uniqueness constraint while populating a unique index.

In this blog post, let’s learn about the error message “20724 Audit fixup process process name found a violation of the uniqueness constraint while populating a unique index.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20724 Audit fixup process process name found a violation of the uniqueness constraint while populating a unique index.

Reason for the Error

A record with a duplicate key from the audit trail was found while populating the index.

Solution

Recover the index file, remove conflicting records from base table and retry

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