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: