LDAP DB corruption after a reindex - "ERR - _entryrdn_insert_key - Same DN (dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,..."

Issue

A database corruption issue related to the entry nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff can happen after a reindexing of a replicated suffix.

LDAP errors log:

[25/Feb/2021:10:34:40.147633966 +0100] - INFO - bdb_db2index - userroot: Finished indexing.
[25/Feb/2021:10:34:42.199441489 +0100] - ERR - _entryrdn_insert_key - Same DN (dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=example,dc=com) is already in the entryrdn file with different ID 133529.  Expected ID is 133541.
[25/Feb/2021:10:34:42.202046664 +0100] - ERR - index_addordel_entry - database index operation failed BAD 1023, err=9999 Unknown error 9999
[25/Feb/2021:10:34:42.220902975 +0100] - ERR - NSMMReplicationPlugin - _replica_configure_ruv - Failed to create replica ruv tombstone entry (dc=example,dc=com); LDAP error - 1
[25/Feb/2021:10:35:12.240676559 +0100] - ERR - _entryrdn_insert_key - Same DN (dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=example,dc=com) is already in the entryrdn file with different ID 133529.  Expected ID is 133541.