Lesson 10: Synchronizing the remote client

In this lesson, you synchronize the remote client for the first time. This is done with the dbmlsync utility. 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.

Prérequis

This lesson assumes you have completed all preceding lessons. See Lesson 1: Designing the schemas.

This lesson assumes you have the roles and privileges listed in the Permissions and privileges section at the start of this tutorial: Tutorial: Using MobiLink with an Oracle Database 10g.

Task

At a command prompt, run the following command:

dbmlsync 
-c "SERVER=remote_eng;DBN=remote_db;UID=DBA;PWD=sql"
-n sync_oracle_publication
-u oracle_remote -mp oracle_pass

dbmlsync is the synchronization application.
SERVER specifies the name of the remote database server.
DBN specifies the name of the remote database.
UID specifies the user name used to connect to the remote database.
PWD specifies the password used to connect to the remote database.
sync_oracle_publication is the publication on the remote device that is used to perform the synchronization. (This publication was created by the Create Synchronization Model Wizard.)
oracle_remote is the user name used to authenticate with the MobiLink server.
oracle_pass is the password used to authenticate with the MobiLink server.

Note

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.

Résultat

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).

Suivant

Proceed to Lesson 11: Viewing the data in the remote database.