<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> David, I can not reproduce this issue. This is what I've done using just 389 DS: <a class="missing changeset" title="No default repository defined">[1]</a> Create two instances: master and dedicated consumer <a class="missing changeset" title="No default repository defined">[2]</a> Setup replication and initialize consumer <a class="missing changeset" title="No default repository defined">[3]</a> Create 4 users on the master: a, b, c, d <a class="missing changeset" title="No default repository defined">[4]</a> do a "db2ldif -r" on the consumer <a class="missing changeset" title="No default repository defined">[5]</a> On master: delete 'c' <a class="missing changeset" title="No default repository defined">[6]</a> On consumer: delete 'd' <a class="missing changeset" title="No default repository defined">[7]</a> do a ldif2db on consumer -> now the consumer has entries: a,b,c,d <a class="missing changeset" title="No default repository defined">[8]</a> Either wait a few minutes, or update entry 'a' on master. <a class="missing changeset" title="No default repository defined">[9]</a> Both master and consumer have entries: a, b This was in a test environment, and there was no replication load. I've tried both (db2ldif/db2ldif.pl & ldif2db/ldif2db.pl) Am I missing any steps? What version of DS were you using? Thanks, Mark </body> </html>