When Identity Manager is not in the master replica server and if some object is moved in the master replica server, there might be multiple sync events generated on the drivers. Some of these sync events are generated before the object move is completed in the master replica server and hence these sync events are not reliable. If some modifications are applied to the moved object in the Identity Manager server, based on any such event, the modifications are ignored because the move is not yet completed in the master replica server.
If you encounter such a situation, check for the timestamp on the <sync> event. If the timestamp shows a value 0#0, it is reliable. If it shows any other value, then it is not reliable.
The following is an example of an unreliable sync event, because it has a timestamp other than 0#0 (marked in bold).
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.5.13.20090903 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<sync class-name="User" event-id="sles10sp3#20130722144515#2#2" from-move="true" qualified-src-dn="O=novell\CN=Auser1" src-dn="\SLES10SP3-TREE\Novell\Auser1" timestamp="1374504315#0">
<association state="associated">{D6B73031-695D-074e-AAAD-D6B73031695D}</association>
</sync>
</input>
</nds>
The following is an example of a reliable sync event, because it has a timestamp 0#0 (marked in bold).
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.5.13.20090903 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<sync cached-time="20130722144516.217Z" class-name="User" event-id="sles10sp3#20130722144515#2#2" from-move="true" qualified-src-dn="O=novell\CN=Auser1" src-dn="\SLES10SP3-TREE\Novell\Auser1" timestamp="0#0">
<association state="associated">{D6B73031-695D-074e-AAAD-D6B73031695D}</association>
</sync>
</input>
</nds>