Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
When you create MobiLink applications with SQL Anywhere remote databases, there are two types of client log file that you should be aware of:
dbmlsync console log
SQL Anywhere transaction log
By default, dbmlsync messages are sent to the dbmlsync console. In addition, you can send the output to a console log file using the -o or -ot options. The following partial command line sends output to a log file named dbmlsync.log.
dbmlsync -o dbmlsync.log ...
Logging dbmlsync activity is particularly useful during the development process and when troubleshooting. Verbose output is not recommended for normal operation in a production environment because it can slow performance.
You can control the size of log files, and specify what you want done when a file reaches its maximum size:
Use the -o option to specify a log file and append output to it.
Use the -ot option to specify a log file, but delete the contents the file before appending output to it.
In addition to -o or -ot, use the -os option to specify the size at which the log file is renamed and a new file is started with the original name.
For more information, see:
You can control what information is logged to the console log file and displayed in the dbmlsync window using the -v option.
For more information, see -v option.
You can manage log files using the delete_old_logs option.
For more information, see delete_old_logs option [MobiLink client] [SQL Remote] [Replication Agent].
When no console log is specified, all output is displayed in the console. When a console log is specified, less output is sent to the console.
See Transaction log files.