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

SQL Anywhere 17 » MobiLink and SAP HANA Remote Data Sync - Client Administration » SQL Anywhere clients for MobiLink » MobiLink SQL Anywhere client utility (dbmlsync) syntax

-n dbmlsync option (deprecated)

Specifies the publication(s) to synchronize.


This option has been deprecated. Use the -s dbmlsync option instead.

To use the dbmlsync -s option you need to determine the subscription name for the subscription you want to synchronize. You can determine the subscription name using the following query:

SELECT subscription_name 
FROM syssync JOIN sys.syspublication 
WHERE site_name = <ml_user> AND publication_name = <pub_name>;

Replace <ml_user> with the MobiLink user you are synchronizing. This is the value specified by the -u option on the dbmlsync command line.

Replace <pub_name> with the name of the publication being synchronized. This is the value specified with the -n option on the dbmlsync command line.

dbmlsync -n pubname ...

You can supply more than one -n option to synchronize more than one synchronization publication.

There are two ways to use -n to synchronize multiple publications:

  • Specify -n pub1,pub2,pub3 to upload pub1, pub2, and pub3 in one upload followed by one download.

    In this case, if you have set extended options on the publications or subscriptions, only the options set on the first publication in the list and its subscription are used. Extended options set on subsequent publications and subscriptions are ignored.

  • Specify -n pub1 -n pub2 -n pub3 to synchronize pub1, pub2, and pub3 in three separate sequential synchronizations.

    When successive synchronizations occur very quickly, such as when you specify -n pub1 -n pub2, dbmlsync could start processing a synchronization when the server is still processing the previous synchronization. In this case, the second synchronization fails with an error indicating that concurrent synchronizations are not allowed. If you run into this situation, you can define an sp_hook_dbmlsync_delay stored procedure to create a delay before each synchronization. Usually a few seconds to a minute is a sufficient delay.