Process to be performed before history and transaction migration

Before you migrate your history and transactions, you must perform a set of tasks.

About this task

Complete the following tasks:

Procedure

Navigate to the <INSTALL_DIR>/Migration/9.5 directory.
When migrating from 9.3, 9.4, or 9.5 to 10.0, run the following command
${ANT_HOME}/bin/ant -Druntime=<INSTALL_DIR> -Druntime.old=<INSTALL_DIR_OLD> -f buildmigration.xml -logfile <logfile> -Dtarget=copyextensions migrate

This command will prepare the extensions package from the old runtime and install it on the new <INSTALL_DIR>

The *.done files created in the 9.5 status folder for the task copyextensions are:
- ant_copyextensions.xml.done
- ant_migrateprops.xml.done
  To customize the web.xml, weblogic.xml, and application.xml files, apply these changes manually in the old runtime.
  
  Note: When performing the postmigration activities, you use the copyextensions target to copy only the standard extensions to the new runtime.
Rename the existing upgradeshared9.5.jar that is present in the <INSTALL_DIR>/Migration/lib/ directory to upgradeshared9.5.jar.bkp. This ensures that the upgradeshared9.5.jar.bkp is not included in the migration class path during 9.5 to 10.0 hop.
When migrating from 9.3, 9.4, or 9.5 to 10.0, run the following command:
```
${ANT_HOME}/bin/ant -Druntime=<INSTALL_DIR> -Druntime.old=<INSTALL_DIR_OLD> -f 
buildmigration.xml -logfile <logfile> -Dtarget=installPCAs migrate
```
Note: This step is optional. It is applicable only if the PCA is installed on the previous release, and it is confirmed that the PCA install on the previous release is supported in the current release.

This command creates a package of all the PCAs installed in the old runtime. Install these packages in the new <INSTALL_DIR>.

The *.done file created in the 9.5 status folder for the installPCAs task is ant_installPCAs.xml.done.

If you are migrating from 9.3 (or later) to 10.0 as part of sharded upgrade, and performing a "colony-by-colony" upgrade, to populate the PCA version numbers of the migrated PCAs, run the following SQL commands in the 10.0 configuration shard:

INSERT INTO SI_VERSION (PRODUCT_LABEL, BUILD_NUMBER, LIC_PROD_VER, SI_COMMENTS) values ('<pca product name>','<pca version#>','<pca version#>','<pca product name>');
If you are using Oracle, before running initupgrade, modify the following scripts to use the correct tablespace:
- SQL queries in <INSTALL_DIR>/Migration/9.5/pre-migration-oracle.sql
- SQL queries in the "ORACLE_Query" nodes of <INSTALL_DIR>/Migration/9.5/history/DropColumnOverride.xml
  Note: If you are upgrading from Release 8.5 (or later), the scripts listed above are not used and do not need to be modified. However, the script listed below should be modified.
- SQL queries in the "ORACLE_Query" nodes of <INSTALL_DIR>/Migration/9.5/transaction/DropColumnOverride.xml
When migrating from 9.3, 9.4, or 9.5 to 10.0, run the following command:
```
${ANT_HOME}/bin/ant -Druntime=<INSTALL_DIR> -Druntime.old=<INSTALL_DIR_OLD> -f 
buildmigration.xml -logfile <logfile> -Dtarget=initupgrade migrate
```
This command performs the following tasks:
- Compares the entity XML files from the previous release with the entity XML files in Release 9.5.
- Generates the alter scripts for shard migration.
  The *.done files created in the 9.5 status folder for the task initupgrade task are:
- history_ant_upgradepreparation.xml.done
- transaction_ant_upgradepreparation.xml.done
If the initupgrade command fails for a reason other than an Invalid Index Definition error and you have to restart this task, run the following commands:
When migrating from 9.3, 9.4, or 9.5 to 10.0, run the following commands:
- ```
${ANT_HOME}/bin/ant -Druntime=<INSTALL_DIR> 
-Druntime.old=<INSTALL_DIR_OLD> -f buildmigration.xml -logfile 
<logfile> -Dtarget=clean-up-for-rerun migrate
```
- From the <INSTALL_DIR>/COM/Migration/9.5/COM_Add-in directory:
```
${ANT_HOME}/bin/ant -f ycdmigration.xml -Druntime=<INSTALL_DIR> -Druntime.old
=<INSTALL_DIR_OLD>
-DYANTRA_RUNTIME_NEW=<INSTALL_DIR>
-Dtarget=clean-up-for-rerun migrate -logfile <logfile>
```
This command deletes the /history and /transaction subfolders located in the <INSTALL_DIR>/Migration/9.5/database/scripts/<db version> directory. This command also deletes the extensions that were copied by running the copyextensions target.
If you are using Oracle, after running initupgrade successfully, modify the generated scripts located in the <INSTALL_DIR>/Migration/9.5/database/scripts/oracle directory to use the correct tablespace. This includes scripts in the /history and /transaction subfolders located in the this directory. For text search indices, the scripts are located in the <INSTALL_DIR>/Migration/9.5/database/scripts/oracle directory.
If you are running an upgrade in sharded mode, perform this step to migrate metadata tables to the new run time.
When migrating from 9.3, 9.4, or 9.5 to 10.0, run the following command:

${ANT_HOME}/bin/ant -Druntime=<INSTALL_DIR> -Druntime.old=<INSTALL_DIR_OLD> -f buildmigration.xml -logfile <logfile> -Dtarget=update-metadata-tables migrate

The *.done file created in the 9.5 status folder for the update-metadata-tables task is transaction_ant_colonyversionmigrator.xml.done.
If you are running an upgrade in sharded mode, perform this step to delete stale records from the PLT_DB_COLONY_POOL table and the PLT_DB_POOL table:
When migrating from 9.3, 9.4, or 9.5 to 10.0, run the following command:

${ANT_HOME}/bin/ant -Druntime=<INSTALL_DIR> -Druntime.old=<INSTALL_DIR_OLD> -f buildmigration.xml -logfile <logfile> -Dtarget=delete-stale-colony-pool migrate

The *.done file created in the 9.5 status folder for the delete-stale-colony-pool task is ant_deletecolonypools.xml.done.
To enhance system performance, you can modify the following properties in the <INSTALL_DIR>/Migration/9.5/buildmigration.properties file:
- yfs.upgrade.no.of.threads.for.tablealters
  This property determines the number of threads that are used to process alter scripts. By default, this value is set to 6. For example, if 10 alters are generated by initupgrade and yfs.upgrade.no.of.threads.for.tablealters is set to 6, 6 threads will process the 10 alters.
- yfs.upgrade.no.of.colonies.in.parallel.for.tablealters
  This property determines the number of colonies that are processed in parallel by the threads running alter scripts. This property is used only for sharded mode. By default, this value is set to 1. For example, if this value is set to 2 and yfs.upgrade.no.of.threads.for.tablealters is set to 6, 6 threads will run for colony1, and 6 threads will run for colony2.