|
Renames and restarts the transaction log.
dbmlsync -x [ size [ K | M | G ] ] ...
You should always specify a size value with the -x option. Specifically, it is recommended that you specify -x 0. Specifying the size avoids potential ambiguity and unintended behavior. When the -x option is specified immediately before the offline-log directory, the size must be specified to avoid errors or unintended behavior.
When the optional size is specified, the log is renamed if it is larger than that size in bytes. Use the suffix k, m or g to specify units of kilobytes, megabytes or gigabytes, respectively. The default size is 0.
If backups are not routinely performed at the remote database, the transaction log continues to grow. As an alternative to using the -x option to control transaction log size, you can use a SQL Anywhere event handler to control the size of the transaction log.