Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » MobiLink - Client Administration » MobiLink SQL Anywhere Client Extended Options

DownloadReadSize (drs) extended option Next Page

ErrorLogSendLimit (el) extended option


Specifies how much of the remote log file dbmlsync should send to the server when synchronization error occurs.

Syntax

el=number[ K | M ]; ...

Remarks

This option is specified in units of bytes. Use the suffix k or m to specify units of kilobytes or megabytes, respectively.

This option specifies the number of bytes of the output log that dbmlsync sends to the MobiLink server when errors occur during synchronization. Set this option to 0 if you don't want any dbmlsync output log to be sent.

When this option is non-zero, the error log is uploaded when a client-side error occurs. Not all client-side errors cause the log to be sent: the log is not sent for communication errors or errors that occur when dbmlsync is not connected to the MobiLink server. If the error occurs after the upload is sent, the error log is uploaded only if the SendDownloadAck extended option is set to ON.

If ErrorLogSendLimit is set to be large enough, dbmlsync sends the entire output log messages from the current session to the MobiLink server. For example, if the output log messages were appended to an old output log file, dbmlsync only sends the new messages generated in the current session. If the total length of new messages is greater than ErrorLogSendLimit, dbmlsync only logs the last part of the newly generated error and log messages up to the specified size.

Note: The size of the output log is influenced by your verbosity settings. You can adjust these using the dbmlsync -v option, or by using dbmlsync extended options starting with "verbose". For more information, see -v option and the -e verbose options:

The default is 32K.

This option has a short form and long form: you can use el or ErrorLogSendLimit.

You can also store extended options in the database. For more information about dbmlsync extended options, see Introduction to dbmlsync extended options.

Example

The following dbmlsync command line illustrates how you can set this option when you start dbmlsync:

dbmlsync -e "el=32k"

The following SQL statement illustrates how you can store this option in the database:

CREATE SYNCHRONIZATION SUBSCRIPTION
   TO sales_publication
   FOR ml_user1
   OPTION el='32k';