Replication conflicts can occur when an incompatible change to an entry is made on two replicas at the same time. The change is processed on one replica and then replicated to the other replica, which causes the conflict. While most conflicts are resolved automatically, some require manual action.
To fix replication conflicts, initialize the replica containing the conflicts with the data from another replica that does not have conflicts. If the database is large and the number of conflicts small, running ldapmodify against the server with the conflict will work if the command includes the Replication Repair Control specified by OID value 22.214.171.124.4.1.30126.96.36.199. The Replication Repair Control prevents the change from replicating. It also enables changing operational attribute values, which are not normally writable.
The following steps provide an example of using the Replication Repair Control to fix replication conflicts by applying change to only the server with the conflict. There are two examples: one for a modification conflict found by performing an ldap-diff, and the other for a naming conflict.