Migration procedure

The files that you need for the database are provided in the FTM artifacts pod and must be downloaded from the pod. For more information about getting files from the artifacts container for your offering, see Getting the files from the artifacts container for your FTM offering.

The following database migration procedures are for FTM 3.2.6.

Db2 on UNIX or the Windows operating system

Note: In this migration procedure, the changes to the EVENT table require the data to be exported or reloaded. To reduce the time that it takes to complete this step, it might be beneficial to review the purge schedule for this table before you do the migration.
  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 /admin/scripts/db2/migration/3.2.6.0_from_3.2.5.0 directory. The files in this directory contain all the database changes since FTM 3.2.5.
  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.