MobiLink Synchronization Reference
  MobiLink Synchronization Client
    dbmlsync options

-x option

Function 

Renames and restarts the transaction log after it has been scanned for outgoing messages.

Syntax 

dbmlsync -x [ size [ K | M | G ]...

Description 

The optional size means that the transaction log is renamed only if it is larger than the specified size. Use the suffix k, m or g to specify units of kilobytes, megabytes or gigabytes, respectively. The default size is 0.

In some circumstances, synchronizing data to a consolidated database can take the place of backing up remote databases, or renaming the transaction log when the database server is shut down.

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 an Adaptive Server Anywhere event handler to control the size of the transaction log. For example, the following event handler renames the transaction log at the remote database when its size exceeds 5 Mb. You can use such an event handler together with the DELETE_OLD_LOGS database option to control the space taken up by transaction logs.

CREATE EVENT RenameLogLimit
TYPE GrowLog
WHERE event_condition( 'LogSize' ) > 5
AT REMOTE
HANDLER
BEGIN
  BACKUP DATABASE DIRECTORY backupdir
  TRANSACTION LOG ONLY
  TRANSACTION LOG RENAME
END

See also 

Automating Tasks Using Schedules and Events

DELETE_OLD_LOGS option [replication]