The remote database is not capable of matching the timestamp precision of the consolidated database. Your application, schema,
and scripts must contain logic that copes with the precision mismatch
Timestamp precision of the consolidated database is found to be higher than attainable by the remote database. If possible
you may lower the timestamp precision on the consolidated database in order to avoid inconsistent timestamp data between the
remote and the consolidated database. Otherwise, you may need to avoid synchronizing timestamps in your synchronization schema;
or you may need to have conflict detection scripts aware of the virtual difference; or you may need to use the -zp command
line option to tolerate the conflict. Your application should also be able to deal with the inconsistency.