Add unique and non-unique indexes

About this task

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 install-transaction-indexes target:
  • <INSTALL_DIR>/Migration/<previous version directory>/database/scripts/<dbtype>/transaction/uniqueindexadds.sql
  • <INSTALL_DIR>/Migration/<previous version directory>/database/scripts/<dbtype>/transaction/indexadds.sql
where <previous version directory> corresponds to the location of the previous version directory and <dbtype> corresponds to the database type (DB2 or Oracle).

This command adds all the unique indexes and nonunique indexes. If nonunique indexes are not to be installed, then the argument -Dnonuniqueindex=Y should not be passed.

Note: Typically, you update the unique transaction indexes by running the install-transaction-indexes target before updating tables by running the upgrade-transaction-tables target. However, if more than one record exists in the YFS_USER table for DISPLAY_USER_ID or ENTERPRISE_CODE or in the YFS_PROPERTY_METADATA table for BASE_PROPERTY_NAME or CATEGORY, you must run the upgrade-transaction-tables target before running the install-transaction-indexes target. Otherwise the install-transaction-indexes target fails because a unique index cannot be created for the respective table.

Nonunique indexes are required for performance improvement. On a large database, nonunique indexes may take a significant amount of time to be installed. You must analyze all the nonunique indexes and verify if all of them are required.