About the FTR Schema Migration Tool

ENOVIA Variant Configuration Central has undergone a major schema design change in V6R2012x. This change improves the current design for scalability and performance, and provides a more concise and understandable schema. The new schema design also converges the ENOVIA Variant Configuration Central data model with that of VPM Central. The ENOVIA Variant Configuration Central Schema Migration Tool helps to facilitate a smooth transition when upgrading a V6R2012 database to V6R2012x.

Important: This is a mandatory migration. It must be run for any ENOVIA Variant Configuration Central customer who is upgrading to V6R2012x, regardless of whether or not FTR data exist.

Schema migration is a post-installation process. For upgrade customers or new customers on an upgraded database, the FTR Schema Migration Tool must only be run AFTER the ENOVIA Variant Configuration Central installation is done.

Related Topics
Running the Migration Tool
Migration Property File Settings
Migration Output Files

The ENOVIA Variant Configuration Central Schema Migration Tool leverages the Common Migration Framework and runs as a multi-step process, as follows:

  1. Find Objects for Pre-Scan—This step queries the objects that need to be scanned for pre-migration.
  2. Perform Pre-Scan—The next step performs pre-migrations, evaluating the structures and determining the migration path.
  3. Find Objects to Migrate—The next step queries the objects that need to be migrated, and writes their object IDs to a series of files.
  4. Scan Data to be Migrated—This step runs through all the logic of the migration step (the next step) but does not commit the changes in order to identify any potential issues that may be encountered during the migration.
  5. Perform Migration—The files created in the previous step are then used to perform the migration for those object IDs.
  6. Clean Up Schema References—The final step cleans up any old schema references.