Importing repotools export - Data mart broken
I am working with a customer who exported their JTS and CCM 3.0.1 databases using the standard repotool commands. They were previously using the Datamart instead of the Data warehouse because they had experienced problems with the data warehouse with their Oracle Database.
The import into the new environment (same URI, but using DB2 instead of Oracle) worked fine, however, the reports are (almost) all broken with this error:
I confirmed in the Eclipse Client that the report templates had all been deployed and the ID's matched. It appears the data mart is broken after this import. Any suggestion on how to fix it?
Side note:
We noticed a setting in "Configure Data Warehouse Connection" regarding "Data Collection Jobs Enabled" and "Import Data-mart data". They were default to "false" while we performed the repotools import. Do they have to be enabled prior to the import in order to bring in the existing data mart?
The import into the new environment (same URI, but using DB2 instead of Oracle) worked fine, however, the reports are (almost) all broken with this error:
Report descriptor not found for: __Y7klHgHEeGkzKo4CAOcmQ
I confirmed in the Eclipse Client that the report templates had all been deployed and the ID's matched. It appears the data mart is broken after this import. Any suggestion on how to fix it?
Side note:
We noticed a setting in "Configure Data Warehouse Connection" regarding "Data Collection Jobs Enabled" and "Import Data-mart data". They were default to "false" while we performed the repotools import. Do they have to be enabled prior to the import in order to bring in the existing data mart?
2 answers
Hi Benjamin,
we upgraded keeping the datamart at another customer.
The data mart is still working with RTC3.0.1.1 but we don't advertise it. there is for that matter no documentation about that it works at all. We ran into some issues. See below how we fixed them.
*1* If you skip the data warehouse setup the data collection jobs for the datamart are disabled. Remove
com.ibm.team.datawarehouse.datawarehouse.jobs.enabled=false
from all teamserver properties. This is created when skipping the data warehouse configuration in the setup and disables all data collection jobs the data mart collection jobs as well as the other ETL jobs to run.
*2* There are several entries of the form:
com.ibm.team.datawarehouse.datawarehouse.*
in the teamserver.properties in JTS and RTC/JAZZ. We deleted them and could run the data collection job again.
* 2.1. Go to https://xxxx/jts/admin#action=jazz.viewPage&id=com.ibm.team.reports.reportsManagementPage
and
* 2.2 Go to https://xxxxxx/jazz/admin#action=jazz.viewPage&id=com.ibm.team.reports.reportsManagementPage
Make sure to select DataMart where the rectangle indicates it
Then run all "Data mart collection jobs" on JTS and RTC and check that the jobs show up in the /admin#action=com.ibm.team.repository.admin.activeServices
we upgraded keeping the datamart at another customer.
The data mart is still working with RTC3.0.1.1 but we don't advertise it. there is for that matter no documentation about that it works at all. We ran into some issues. See below how we fixed them.
*1* If you skip the data warehouse setup the data collection jobs for the datamart are disabled. Remove
com.ibm.team.datawarehouse.datawarehouse.jobs.enabled=false
from all teamserver properties. This is created when skipping the data warehouse configuration in the setup and disables all data collection jobs the data mart collection jobs as well as the other ETL jobs to run.
*2* There are several entries of the form:
com.ibm.team.datawarehouse.datawarehouse.*
in the teamserver.properties in JTS and RTC/JAZZ. We deleted them and could run the data collection job again.
* 2.1. Go to https://xxxx/jts/admin#action=jazz.viewPage&id=com.ibm.team.reports.reportsManagementPage
and
* 2.2 Go to https://xxxxxx/jazz/admin#action=jazz.viewPage&id=com.ibm.team.reports.reportsManagementPage
Make sure to select DataMart where the rectangle indicates it
Then run all "Data mart collection jobs" on JTS and RTC and check that the jobs show up in the /admin#action=com.ibm.team.repository.admin.activeServices
Thank you! This is exactly what we found as well. It turns out you should *always* copy the conf properties files from the migrated server to the new server, and double check to make sure the value for the datamart is set to true - this is definitely what caused the first import to skip importing the data mart.
Thank you - we have resolved this issue.
Thank you - we have resolved this issue.