Back up your JRE directory   Upgrading may overwrite the JRE directory (%SQLANY16%\binXX\jre170) and its subdirectories. In this case, if you are using certificates, your certificate store (%SQLANY16%\binXX\jre170\lib\security\cacerts) is overwritten, including your certificates. Similarly, fonts you added to the %SQLANY16%\binXX\jre170\lib\fonts\fallback directory to help display characters in the administration tools may be lost. To minimize upgrading steps with regard to the JRE change, create a backup copy of the JRE directory and all of its subdirectories before you upgrade so that you can refer to or restore files (such as cacerts) from the backup, as needed.

Check the behavior changes   Confirm that none of the documented behavior changes affect your application. If they do, update your application. See What's new in version 16.0.

Test your application   Test your application thoroughly in a SQL Anywhere 16 environment before upgrading any applications in production use.

Use the correct version of the utilities   Make sure that you use the correct version of the database utilities with your new database. See How to ensure that you are running the correct version of the utilities when you have multiple versions installed.

Validate and back up the database   Before you begin an upgrade, validate your database, and back up your software and database. To ensure future recoverability, back up the database when you finish the upgrade.

Synchronize before upgrading   For databases involved in synchronization, such as UltraLite databases or SQL Anywhere remote databases in MobiLink installations, perform a successful synchronization before upgrading.

Test your upgrade procedure   Test your upgrade procedure carefully before carrying it out on a production system.