Migration of RTC 2.0.0.2 Data Warehouse Extension to Rational Team Concert 3.0.1.4
We have deployed a data warehouse extension in Rational Team Concert 2.0.0.2 that added some tables and views to the data warehouse. The data base implementation is Oracle 11G.
I have read that when upgrading from RTC 2.0 to 3.0 that the old data warehouse data becomes a data mart that can be migrated into a new data warehouse.
Will the data in the two custom tables successfully migrate into a 3.0.1.4 data warehouse, or will the data need to be migrated over manually in Oracle?
If the RTC 2.0.0.2 data warehouse extension does not work with the 3.0.1.4 data warehouse could we continue to use it with the 3.0.1.4 data mart instead?
One answer
Hello,
I don't think your custom tables will migrate to the new data warehouse as the migration code does not know about your customizations. However, it is possible to remain operating in datamart mode rather than switch to the data warehouse.
When you upgrade to 301x, select the option to 'skip' data warehouse setup.
See this wiki topic where it discusses what it calls 'local' mode: https://jazz.net/wiki/bin/view/Main/CALMReportingMigration
In fact, your scenario is discussed under this question 'Why might a customer want to keep LOCAL?'
I don't think your custom tables will migrate to the new data warehouse as the migration code does not know about your customizations. However, it is possible to remain operating in datamart mode rather than switch to the data warehouse.
When you upgrade to 301x, select the option to 'skip' data warehouse setup.
See this wiki topic where it discusses what it calls 'local' mode: https://jazz.net/wiki/bin/view/Main/CALMReportingMigration
In fact, your scenario is discussed under this question 'Why might a customer want to keep LOCAL?'