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.

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.4.0_from_3.2.3.0 directory. The files in this directory contain all the database changes since FTM 3.2.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.
  5. The following tables need to be checked for Check or Reorg Pending status:
    • VALUE
    • H_VALUE
    • USAGE_INSTANCE_BASE
    • CALENDAR_GROUP
    • H_CALENDAR_GROUP
    • SCHEDULE_ENTRY
    • H_SCHEDULE_ENTRY
  6. Optional Step: The TCP/IP loopback node is no longer being created for the FTM database. If you want to remove this node, use the UnCatLoop_Optional script.