Migration procedure

Note: You do not need to run this migration procedure if you already ran either of the following database migration steps:
  • From version 3.0.0, Fix Pack 10 to version 3.0.0, Fix Pack 11
  • From version 3.2.0, Fix Pack 2 to version 3.2.0, Fix Pack 3

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.

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 /admin/scripts/db2/migration/3.2.2.0_iFix2_from_3.2.2.0 directory. The files in this directory contain all the database changes since FTM 3.2.2. No database changes were made in 3.2.2, interim fix 1.
  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.