Migration procedure

Db2

  1. Create a backup of the database to be migrated so that it can be rolled back if a problem occurs during or after the migration process.
  2. Start a command window that has Db2® administrative privileges.
  3. Go to the instdir/ftm/v322/admin/scripts/db2/migration/3.2.2.0_from_3.2.0.3 directory. The files in this directory contain all the database changes since FTM 3.2.0, Fix Pack 3.
  4. Run one of the following scripts:
    • Migrate-Win.cmd [Database Name] [Database Schema] [Database User] [Password] - Main Windows operating system script to update the database.
    • Migrate-Unix.sh [Database Name] [Database Schema] [Database User] [Password] - Main UNIX script to update the database.
Note: The alter column statements put the CLASSIFICATION and H_CLASSIFICATION tables into a REORG PENDING state. Reorganize the tables by using the REORG TABLE command.

Oracle

  1. Create a backup of the database to be migrated so that it can be rolled back if a problem occurs during or after the migration process.
  2. Start a command window that has Oracle administrative privileges.
  3. Go to the instdir/ftm/v322/admin/scripts/oracle/migration/3.2.2.0_from_3.2.0.3 directory. The files in this directory contain all the database changes since FTM 3.2.0, Fix Pack 3.
  4. Run one of the following scripts and follow the prompts. You need the FTM username and password, and the Oracle database user and password:
    • Migrate-Win.cmd [Database Name] [Database Schema] - Main Windows operating system script to update the database.
    • Migrate-Unix.sh [Database Name] [Database Schema] - Main UNIX script to update the database.