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

SQL Anywhere 11.0.1 (Français) » MobiLink - Getting Started » MobiLink Tutorials » Tutorial: Using MobiLink with an Oracle 10g consolidated database


Lesson 7: Synchronize

Now you are ready to synchronize the remote client for the first time. This is done with the MobiLink client program dbmlsync. Dbmlsync connects to the remote database, authenticates itself with the MobiLink server, and performs all the uploads and downloads necessary to synchronize the remote and consolidated databases based on a publication in the remote database.

♦  To synchronize the remote client

The progress of the synchronization appears in the SQL Anywhere MobiLink Client Messages window. When this command runs successfully, the dbmlsync application populates the remote database with a subset of information from the consolidated database.

If synchronization fails, check the connection information you pass to the dbmlsync application, and the MobiLink user name and password. Failing that, check the publication name you used, and ensure that the consolidated database and MobiLink server are running. You can also examine the contents of the synchronization logs (server and client).


If you are running the dbmlsync application on a different computer from your MobiLink server, you must pass in arguments that specify the location of the MobiLink server.

View the data

After successfully synchronizing the remote client to the consolidated database through the MobiLink server, the remote data should be populated with information relevant to one salesperson. You can verify this in Sybase Central using the SQL Anywhere 11 plug-in.

♦  To view the data in the remote database
  1. Start Sybase Central

  2. Connect to the remote database:

    1. On the left pane, right-click SQL Anywhere 11 and choose Connect.

    2. Type DBA as the User Id and sql as the Password.

    3. Under the Database tab, type remote_eng as the Server Name and remote_db as the Database File.

    4. Click OK.

  3. Choose the ORDERS table and then click the Data tab on the right pane.

    In the ORDERS tables, all the records are for the salesperson with an identifier of 154. This particular salesperson is not concerned with the sales information of other salespeople. For this reason, you set the synchronization scripts to filter out rows by the remote ID, and you set this database's remote ID to the value of a particular salesperson identifier. Now this particular salesperson's database takes up less space, and requires less time to synchronize. Since the remote database size is kept to a minimum, frequently performed operations such as entering a new sale or processing a refund on a previous sale runs faster and more efficiently.

Further reading