Contents Index 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 The timestamp precision mismatch may be resolved by setting the DEFAULT_TIMESTAMP_INCREMENT option on the remote database to %1!d! and TRUNCATE_TIMESTAMP_VALUES to 'On'

MobiLink Synchronization Reference
  MobiLink Synchronization Server Warning Messages
    MobiLink synchronization server warning descriptions

The timestamp precision mismatch may affect upload conflict detection. Use the -zp option to cause the MobiLink synchronization server to use the lowest timestamp precision for conflict detection purposes

Item Value
Warning code 10020
Level 3
Probable cause 

Timestamp precision mismatch between the remote database and the consolidated database has been detected. The mismatch can affect upload conflict detection as the MobiLink synchronization server will compare the rows for the two databases. If you decided not to align precision on the databases involved in your synchronization system, you may use the -zp swith to start the MobiLink synchronization server.

If this switch is used, the MobiLink synchronization server will tolerate conflict caused by timestamp differences smaller than the lower precision among the two databases.

Contents Index 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 The timestamp precision mismatch may be resolved by setting the DEFAULT_TIMESTAMP_INCREMENT option on the remote database to %1!d! and TRUNCATE_TIMESTAMP_VALUES to 'On'