IBM TDI 7.1 uses Derby v10.3 as its bundled database, used by default by the System Store. We will need to migrate your existing Cloudscape or Derby databases (created using previous versions of TDI) to be able to use TDI 7.1. Derby v10.3 drivers that are shipped with TDI 7.1 cannot be used to communicate with older versions of Cloudscape.
For details, and information on differences between Cloudscape/Derby v10 and its prior versions, refer to the following web page:http://publibfp.boulder.ibm.com/epubs/html/c1894710.html.
Notable differences that have an immediate impact are as follows:
Connection type | Cloudscape v5.1 | Derby v10 |
---|---|---|
Embedded Derby / Cloudscape | jdbc:db2j: | jdbc:derby: |
DB2 JDBC Universal Database Driver (Network mode) | jdbc:db2j:net | jdbc:derby:net (Not recommended to use) |
DerbyClient Driver | - | jdbc:derby (Recommended) |
Fortunately, the Derby team have provided a migration utility that migrates a Cloudscape v5.1 database to a new Derby v10 database. It migrates all the tables and their corresponding data into a newly generated Derby v10 database. It modifies all tables with varbinary datatype to BLOB datatype, hence making the migration process quite painless.
This utility is bundled with TDI 7.1, in the TDI_install_dir/tools/CSMigration folder, along with a wrapper script that invokes the migration tool, called migrateCS.bat(sh). To migrate a Cloudscape 5.1 System Store Database created using TDI v6.0 to Derby v10, we have to invoke the migrate script in the following manner:
migrateCS [Path_of_CloudscapeV51_Database] [Path_of_new_DerbyV10_Database]
You may need to give some thought to the location of the new Derby database. In TDI v6.0 and v6.1.x, the System Store database often was located in the installation directory of TDI; this is an unfortunate location for many reasons. For TDI 7.1 we strongly recommend we use a Solution Directory, away from the installation directory.
Besides migration of data, you also need to modify your global.properties / solution.properties files (using the migration tool or manually) to incorporate the new JDBC URL parameters.