Migration from an earlier TM version to V2 must consider that the SQL database engine used in TM was changed in this version to SQLite (a free OpenSource application that can be deployed with no restrictions).
Upgrading from an earlier version to V2 requires a database migration from MySQL to SQLite.
Only system configuration parameters will be migrated:
Existing TM systems will be preserved
Database tables will be modified to the V2 database schema
RG and Quality of Service Configuration parameters will be preserved
TM - User accounts
User defined Advanced Queries
Trace data files, including Telephony Control Server RTT, RG, and OSB, will need to be re-processed by the DIPAZ utility to populate the database during the upgrade process, or the administrator has the option to perform a Clean Start.
Upgrading from V1 will automatically update 3rd. Party products and base software.
Only systems running TM V1R2.5.7 and TM V1R3.7.0 or V1R3.8.0 can upgrade directly to TM V2R0.
Upgrading from earlier TM versions directly to V2 is not supported. If you are running a version that is earlier to V1R2.5.7 then you will be required to first upgrade to V1R3.8.0.
Upgrading to a New TM (Lotus Sametime Unified Telephony-Trace Management) Version