After Installing
Page 5 of 6

Upgrades

To connect to a database created with a version of Cloudscape prior to 3.6, Cloudscape must upgrade that database. Upgrading involves writing changes to the system tables, so it is not possible for databases on read-only media. (For information about upgrading read-only databases, see Read-Only Databases and Upgrading). The upgrade process makes the following changes:

  • adds new columns to one system table (SYS.SYSCOLUMNS)
  • updates the data dictionary version information
  • removes any existing JDBC metadata stored prepared statements

    If you have cloudscape.jdbc.metadataStoredPreparedStatements set to dynamic or onDatabaseCreation, existing metadata stored prepared statements are deleted during the upgrade. They will be re-created dynamically as needed.

  • adds a new class alias
  • for Cloudscape synchronization systems, automatically upgrades DDL statements waiting to be replayed at targets during the refresh

NOTE: If Cloudscape is upgrading a database from a version before Version 3.5, it makes additional changes.

NOTE: Be sure to read the Release Notes for information about Beta databases and upgrade.

Recommended Steps Before Upgrading

Upgrade happens the first time the new Cloudscape software connects to the old database. Before connecting with the new software, perform the following steps:

  1. Force a checkpoint with the pre-3.6 version of the software, so that recovery need not be run during the upgrade and to minimize the time for the upgrade to complete. To accomplish this, connect to the database with the pre-3.6 version of the Cloudscape software and issue a shutdown request using the shutdown=true attribute on the database connection URL:

    /* in a java program */
    DriverManager.getConnection("jdbc:cloudscape:;shutdown=true");

    Cloudscape tools always perform a shutdown in an embedded environment.

    Opening a local connection to your database with the pre-3.6 version of Cloudview and then exiting causes the same command to be issued.

  2. Back up your database. (Copy the entire system directory, including the entire database directory and the cloudscape.properties file if one exists, to a safe location.)

    Once the database is upgraded to 3.6, it cannot be changed back to the Version 3.5 format.

Upgrading a Database

To upgrade a database, you must explicitly request an upgrade the first time you connect to it with Cloudscape Version 3.0 or higher. You explicitly request an upgrade with the database connection URL attribute upgrade=true. For example:

jdbc:cloudscape:toursDB;upgrade=true

Once the upgrade is completed, you cannot connect to the databases with an older version of Cloudscape.

NOTE: Do not attempt to convert a database to a source (convertToSource=true) before upgrading its software version. Do not attempt to upgrade a database without backing it up.

You can find out the version of Cloudscape with the following command:

java COM.cloudscape.tools.sysinfo

NOTE: Note that this is the product version, not the database version. It uses information in the jar files, so verify that only one Cloudscape product's jar files are in your class path when you run this tool.

Synchronization Databases and Upgrades

Cloudscape supports automatic upgrade for synchronization databases.