After Installing,
Page 5 of 6


[top]
[prev]
[next]
Documentation Top
Global Index
Reference Manual
TOC Index
Grammar index
Developer's Guide
TOC Index
Tuning Cloudscape
TOC Index

Upgrades

To connect to a database created with a version of Cloudscape prior to 3.0, 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:

  • recompiles all stored prepared statements
  • adds a new system table
  • replaces one system table
  • adds new columns to some system tables and drops others
  • adds log records
  • 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.
  • For Cloudscape synchronization systems, DDL statements waiting to be replayed at targets are automatically upgraded during the refresh.
  • For Cloudscape synchronization systems, adds indexes to existing system tables.
  • For Cloudscape synchronization systems, sets some internal database properties.

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 connections to the old database. Before connecting with the new software, perform the following steps:

  1. Force a checkpoint with the 2.0.x release, 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 a 2.0.x 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 3.0 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.0, it cannot be changed back to the 2.0 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. 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.

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

NEW: Cloudscape supports automatic upgrade for synchronization databases.

[top]
[prev]
[next]


Cloudscape Version 3.0
For technical support, go to: www.cloudscape.com and click Support.
Copyright © 1998 and 1999 Cloudscape, Inc. All rights reserved.