Migration procedure

Note: If you already ran the steps to migrate the database from version 3.0.0, Fix Pack 10 to version 3.0.0, Fix Pack 11, you do not need to run this 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/v320/admin/scripts/db2/migration/3.2.0.3_from_3.2.0.2 directory. The files in this directory contain all the database changes since FTM 3.2.0, Fix Pack 2.
  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.

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/v320/admin/scripts/oracle/migration/3.2.0.3_from_3.2.0.2 directory. The files in this directory contain all the database changes since FTM 3.2.0, Fix Pack 2.
  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.