What Data Warehouse job do we run after upgrading from RTC 2.0 to 3.0.1.4 and customer uses BIRT
We recently migrated a customer who has custom BIRT reports from RTC 2.0 to 3.0.1.4 and after migration was complete we noticed some reports don't go back in time as far as we expect. For example, when we set a parameter to retrieve from Jan12 - Mar12 it returns nothing, but does for all months after. Prior to migration it reported on data back to 2011. There are a few reports related to Defect Backlogs that do report this data though so it seems the issue is more with the individual reports rather than the Data Warehouse.
But just to be safe I wanted verify which jobs we run after the migration:
On the Reports tab do we need to run the Full Data Collection Job or just the incremental one.
But just to be safe I wanted verify which jobs we run after the migration:
On the Reports tab do we need to run the Full Data Collection Job or just the incremental one.
2 answers
Hi Michael,
I am not sure if you have fixed your issue but the answer is following:
Usually incremental jobs are enough. But if incremental does not fix your issue check into jazz-etl.log file for any error. You might have any messages there which can be useful for further analyzis.
RTC 3 enables new data warehouse model (called data warehouse). Do you use Data mart or data warehouse? It might be the issue with that. You can check it in admin panel in reports section.
Finally, you can always try running full data warehouse job to check if it fixes the issue.
Let us know if it helps.
I am not sure if you have fixed your issue but the answer is following:
Usually incremental jobs are enough. But if incremental does not fix your issue check into jazz-etl.log file for any error. You might have any messages there which can be useful for further analyzis.
RTC 3 enables new data warehouse model (called data warehouse). Do you use Data mart or data warehouse? It might be the issue with that. You can check it in admin panel in reports section.
Finally, you can always try running full data warehouse job to check if it fixes the issue.
Let us know if it helps.