Reporting showing data from before upgrade (upgraded RTC 2.0 to RTC 4.0)
In December 2012, I decided to upgrade from RTC 2.0 to RTC 4.0. The process was time consuming, so I decided to leave reporting and DW unconfigured, ie. I ticked the flag when running ‘/jts/setup’ as shown on the following picture (sorry for the screenshots being in Polish). When I finally found the time to have the reporting configured, I came back to ‘/jts/setup’ and ‘unticked’ the checkbox. I had already DW database created. Passed all the configuration parameters that I needed, except for the etl_user form, which was grayed out. Report background jobs were failing with an error, that on the server side in the logs looked like this:
I managed to created etl_user manually as described in this article.
After I did that, background jobs for reporting stopped signalling errors, and what I could see in the logs is:
The job was running for nearly 2 days. The log and the time it took to execute, made me sure that the background jobs are working correctly. However, when I started executing standard reports There was no data in them. When I started modifying the parameters, it turned out that the reports are only able to display data that was created before December 2012. I stopped at this point, as I cannot figure out why the new reports (I have a new eclipse installation for RTC 4.0) are behaving as if they were digging in RTC 2.0 reporting data, rather than in new RTC 4.0 DW database.
Can someone point me in the right direction? |
One answer
In RTC 2.0 we used a Data Mart configuration, and in 3.x and 4.x we use a Data Warehouse. Typically, your first ETL job will migrate the data from the data mart into the DW, and then collect new information. In your case, it appears that you are only collecting historical information from the data mart.
On your Data Collection page under JTS, https://server:9443/jts/admin#action=com.ibm.team.reportsManagement.etlConfig Check that the DW section lists jobs, and each are selected. This means you are using DW. If the section indicating Data Mart has jobs listed, this means you are using DM. Comments I've checked the jobs under the URL you gave and they look fine: and the status of the jobs is also OK (on the 25th I configured etl_user, so before that date the tasks were failing):
I also checked the same for 'CCM'. The results also show that everything seems to be OK
The results of running the jobs look like this:
I've put here the items from before I configured etl_user to show that previously the jobs were failing. I also noticed that 'Work Items Migracja' (in english this would be 'Work Items Migration') was executed with status OK.
After that there was this long-running work items collection task that ran for almost two days:
'1 dzień 17 godz.' means '1 day 17 hrs' in english.
If you have a clue if my problem is with the server side, or with the client side, I'd be happy to hear the remarks. What I mean by 'client-side' is that I'm using reports that I import from the following folder of my eclipse installation:
Maybe I have the wrong version of the reports?./plugins/com.ibm.team.examples.reports.common_3.1.200.v20121020_1351 That looks OK. Can you edit your report parameters? Sometimes the default is selected "My Team Areas" but if you are not apart of a team area this may cause no work items to show. Try playing around with the different report parameters and see if it prompts the report to show (this is done by clicking the edit button in the top right hand corner)
showing 5 of 7
show 2 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Cześć Dominik,
First thing you need to check is whether your etl jobs run correctly. Navigate to https://your-server:9443/ccm/admin#action=com.ibm.team.reportsManagement.etlStatus to see whether your status is green or red.
If it is red, please check ccm-etl.log files.
Feel free to notify us about the results of the investigation.
Thank you for your interest. As I have written in my detailed problem descriptions, my background jobs run fine. I did not mention that the status is 'green', maybe I should have. But you could also deduce that from the logs that I've included.