Run alter-transaction-tables command

About this task

This command performs preparatory tasks before performing an upgrade. This includes getting the size of tables to determine which tables will take longer to upgrade, and dropping the views. This information is used later when performing the actual upgrade so as to minimize the time.

It then uses the size information available, and performs alterations to the transaction tables. After this task is performed, the transaction tables will have new columns and data. Values in the transaction tables are trimmed for the data types that have been changed in the newer version.

Note: If you set the yfs.apply.sql.manually property to Y in the <INSTALL_DIR>/Migration/9.3/buildmigration.properties file, you must manually apply the following DDLs before running the alter-transaction-tables target:
  • <INSTALL_DIR>/Migration/<previous version directory>/database/scripts/<dbtype>/transaction/uniqueindexdrops.sql
  • <INSTALL_DIR>/Migration/<previous version directory>/database/scripts/<dbtype>/transaction/indexdrops.sql
  • <INSTALL_DIR>/Migration/<previous version directory>/database/scripts/<dbtype>/transaction/alters.sql
  • <INSTALL_DIR>/Migration/<previous version directory>/database/scripts/<dbtype>/transaction/seq.sql
where <previous version directory> corresponds to the location of the previous version directory and <dbtype> corresponds to the database type (DB2 or Oracle). However, when upgrading from Release 8.2 (or earlier), exclude alters in the above files that belong to tables mentioned against the yfs.migrator.exclude.tables property in the <INSTALL_DIR>/Migration/<previous version directory>/buildmigration.properties file.