Supported migrations

Edit online

Migration of databases is supported for most of the Engineering Lifecycle Management applications. Review the applications and repositories that are supported before your start the database migration.

Application repositories that can be migrated

The repositories of the following Engineering Lifecycle Management applications can be exported and imported by using the exportConcurrent and importConcurrent repotools commands:
  • Jazz® Team Server
  • IBM® Engineering Requirements Management DOORS® Next
  • IBM Engineering Workflow Management
  • IBM Engineering Test Management
  • IBM Engineering Lifecycle Optimization Engineering Insights
  • Global Configuration Management
The following applications do not use a relational database and do not need migration:
  • Lifecycle Query Engine
  • Link Index Provider

Migration scenarios

Currently, migration is supported for the following scenarios:
  • Microsoft SQL Server to Db2
  • Microsoft SQL server to Oracle Enterprise Edition DB

Application repositories that can be migrated by other methods

Migrating the following repositories involves methods other than the repotools commands:
  • Repositories that are available in a data warehouse:
    • The reports that are built by using the data in a data warehouse might not return the correct data when built by using data from another data warehouse.
    • For Data Collection Component database, create a new database in the new environment.
    • You might lose trends when you migrate your database from a data warehouse to a different vendor. To retain your trend data, see How can you keep your trend data after migrating data warehouse database to different vendor.
  • To migrate database of the IBM Engineering Lifecycle Optimization - Publishing:

    For migrating data from SQL server to Db2, see Migrating data from SQL server to Db2.