Peer-to-peer replication error

Edit online

If you are running peer-to-peer replication, you might encounter the error "No such object occurred for replica." Follow the steps to resolve this problem.

You might see an error similar to the following error:
 09/07/04 12:57:10 Error No such object occurred for replica 'CN=SERVER2,
CN=SERVER3,IBM-REPLICAGROUP=DEFAULT,O=IBM': modify failed for entry 
'CN=MISSING_ENTRY' change ID 5109011.
where CN=SERVER2 and CN=SERVER3 are the peer servers and CN=MISSING_ENTRY is the entry on which the error occurred.

One common cause of this error is that peer-to-peer replication, by design, does not allow for conflict resolution.

To correct this error, complete the following steps:

  1. Locate the entry that is listed under the "No such object occurred for replica" error in the Server log (ibmslapd.log).
  2. Use the idsdb2ldif command to export the entry or entries in the log from the peer server on which the error or errors occurred; for example: 
    idsdb2ldif -o out.ldif -I instance name -s subtree DN
    where:
    • out.ldif is the name of the file to which you want to export the entry.
    • instance name is the name of the instance.
    • subtree DN is the DN of the entry you want to export.
  3. Use the idsldapadd command to import the entry to the other peer server; for example: 
    idsldapadd -D cn=root -w secret -i out.ldif
    where out.ldif is the name of the file that contains the entry that you want to import.