Teach you how to upgrade to SQL Anywhere 10 (9)

Upgrading the Mobilink Server

Before using the Mobilink Server version 10, carefully review whether the behavior changes will affect the application.

The Mobilink server version 10 supports only versions 8 and 9 of SQL anywhere and Ultralite clients. If you need to support an earlier version of the client, you can keep an earlier version of the Mobilink server.

upgrading SQL Anywhere Mobilink clients

In a production environment, only the SQL anywhere remote database needs to be upgraded after the consolidated database and Mobilink server are upgraded.

Attention:

In version 10, Adaptive Server anywhere has been renamed to SQL anywhere.

There are several upgrade considerations:

• Upgrade Software

• Upgrading the remote database itself

• Upgrade the entire application

Attention:

Perform a successful synchronization before you upgrade the database with the Mobilink synchronization environment. You must also validate and back up the database.

Upgrade software

We recommend that you upgrade both the Dbmlsync Mobilink client and the SQL anywhere database at the same time. Be sure to upgrade the remote database before running the new Dbmlsync utility.

The Mobilink Client for version 10 requires a version 10 Mobilink synchronization server to synchronize with it. Version 10 clients cannot synchronize with an earlier version of the Mobilink server.

Upgrading remote Databases

You can upgrade the Mobilink SQL anywhere remote database by using the above methods for upgrading the SQL anywhere database.

In some cases, such as schema changes or important database changes, you may need to perform manual uninstallation and loading.

Manually uninstall and load the SQL anywhere database

1. Successfully perform the synchronization and verify and back up the remote database.

2, run the Dbtran utility to display the start offset and end offset of the database transaction log. You need to pay attention to the end offset.

3, rename the transaction log. This ensures that it is not changed during the uninstallation process. Copy the renamed log files to a secure location, such as an offline directory.

4, unload the database.

5, initialization of the new database.

6, load the data into the new database.

7, close the new database.

8, erase the new database transaction log.

9. Use the following steps to run DBLog on the new database:

Use the-z option to specify the end offset that you noted in step 2nd.

Use the-X option to return the appropriate offset to zero.

For example:

Dblog-x 0-z 137829 database-name.db

10, start Dbmlsync, specify the location of the original log file removed in step 2nd.

11, when you no longer need the old log files, you can set the Delete_old_logs database options.

Upgrade Application

When deploying a new version of the Mobilink application, it is recommended that you use the new version name in the synchronization script. For example, if the version named V1 is already applied, the upgraded application can use the version name v2. You can use two version names at the same time. This makes it easier to step through the remote database, rather than completing it all at once.

In version 9.0.0 and later versions, the-ZD option for the Mobilink server has been removed. If you want to upgrade your deployment using the-ZD option system, you must change the download script to accept the most recent download timestamp (last download timestamp) as the first parameter.