Adaptive Server Anywhere Client Synchronization Parameters
Renames and restarts the transaction log after it has been scanned for outgoing messages.
dbmlsync -x [ size [ K | M | G ]...
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 If event_parameter( 'NumActive' ) <= 1 then BACKUP DATABASE DIRECTORY backupdir TRANSACTION LOG ONLY TRANSACTION LOG RENAME end if; END
In this example, NumActive ensures that only one of the stacked handlers is executed.
SQL Anywhere Studio 9.0.2
Copyright © 1989–2004 Sybase, Inc. Portions copyright © 2001–2004 iAnywhere Solutions, Inc. All rights reserved.