Contents Index Customizing synchronization Concurrency during synchronization

MobiLink Synchronization User's Guide
  Adaptive Server Anywhere Clients
    Initiating synchronization

Transaction log files


To prepare the upload stream, the dbmlsync utility requires access to all transaction logs written since the last successful synchronization. However, log files are typically truncated and renamed as part of regular database maintenance. In such a case, old log files must be renamed and saved in a separate directory until all changes they describe have been synchronized successfully.

You can specify the directory that contains the renamed log files on the dbmlsync command line. You may omit this parameter if the working log file has not been truncated and renamed since you last synchronized, or if you run dbmlsync from the directory that contains the renamed log files.

For more information, see Backup and Data Recovery.

Example 

Suppose that the old log files are stored in the directory c:\oldlogs. You could use the following command to synchronize the remote database.

dbmlsync -c "dbn=remote;uid=syncuser" c:\oldlogs

The path to the old logs directory must be the final argument on the command line.


Contents Index Customizing synchronization Concurrency during synchronization