Migrating existing Transaction Reporter data

When you upgrade ITCAM for Transactions from V7.4 to V7.4.0.1 and later, existing Transaction Reporter data such as baselines and topology is saved to a backup directory. Migrate this historical data if required.

Before you begin

Fast path: If you have applied an interim fix between releases, the migration process described here may not be required. If you applied interim fix 7.4.0.0-TIV-CAMTT-IF0015 or later and Transaction Reporter was not included in the update, you can skip this migration process.

For 7.4.0.0-TIV-CAMTT-IF0015 and later, the Transaction Reporter (TO agent) checks and logs the version of the history, warehouse, and baseline database files. In the Transaction Reporter logs, the version return value indicates if you need to complete the migration process:

If the version is less than 300, complete the migration
If the version is 300, 7.4.0.0-TIV-CAMTT-IF0015 has been applied and no further migration is necessary

For example, in the following log excerpt, the version is 300, so no migration is required:

cat ITMHOME/logs/hostname_to_uuid-01.log | grep "Schema" ... 
TransactionReporterAgent") Schema history.db version 300 expected 300 check OK ...

Ensure that you have sufficient disk space to migrate the Transaction Reporter data. Check the size of the existing ITM_HOME/arch/to/bin/todata or backup directory. You will need at least 2.5 times the space of the current directory to successfully migrate the data.

Restriction: If the Transaction Reporter data directory is large, the tool may take some time (possibly hours) to migrate the data, depending on your disk I/O speed .

Procedure

To migrate existing Transaction Reporter data:

Stop the Transaction Reporter.
Check that a backup copy of the ITM_HOME/arch/to/bin/todata directory was saved by the installer. The installer renames the directory by appending a timestamp, that is, ITM_HOME/arch/to/bin/todata_YYYYMMDDHHMM. If no backup directory exists, create one.
For UNIX and Linux systems, ensure that ITM_HOME/arch/to/bin/todata is empty.
Set the library path:
- For AIX systems, LIBPATH=ITM_HOME/aix536/to/lib:ITM_HOME/tmaitm6/aix536/lib
- For Linux systems, LD_LIBRARY_PATH=ITM_HOME/lx8263/to/lib:ITM_HOME/tmaitm6/li6263/lib
- For zLinux systems, LD_LIBRARY_PATH=ITM_HOME/ls3263/to/lib:ITM_HOME/tmaitm6/ls3263/lib
- For Solaris systems, LD_LIBRARY_PATH=ITM_HOME/sol293/to/lib:ITM_HOME/tmaitm6/sol283/lib
- For Windows systems, PATH=%PATH%;GSKit_HOME\lib;ITM_HOME\TMAITM6\tosupport
  For example, PATH=C:\IBM\ITM\TMAITM6\bin;C:\IBM\ITM\GSK8_x64\lib;C:\IBM\ITM\TMAITM6\tosupport
Run ITM_HOME/aix536/to/bin/toUpgradeTool. Specify the location of the following directories:
- ITM_HOME. For example, /opt/ibm/itm
- The back up of the Transaction Reporter data directory containing the data to migrate which was specified in step 2. For example, ITM_HOME/arch/to/bin/todata_20150710T112728
- The output directory. For example, ITM_HOME/arch/to/bin/todata
Wait for the data to migrate.
When the migration is complete, for zLinux and xLinux, check that MetaData.xml was copied to the ITM_HOME/arch/to/bin/todata/topology directory. If the file is missing, copy the file manually.
Restart the Transaction Reporter.
Tip: Check the Transaction Reporter logs for any problems. Search for todata in the logs.

What to do next

If required, delete or back up the ITM_HOME/arch/to/bin/todata_YYYYMMDDHHMM directory described in step 2 above.