Is there a way to run a full ETL load automatically?
During a few months the results from the partial loads were not being monitored, and it turns out that some daily jobs kept failing for months until someone noticed it.
We identified and fixed the issues, and now the daily jobs are finishing successfully on a daily basis.
However, we noticed some gaps in the DW database because some reports containing records created during the period the jobs were failing are incomplete.
I understand I need to run a full ETL load to fix this, since the documentation says the full load job rebuilds all the data warehouse tables from scratch.
My question is: is there a way I can start the full load so that all jobs will be executed automatically? Or do I have to run them one by one manually, obeying this sequence:
- Jazz Team Server/Common and Repository
- Rational® Team Concert/Common and Repository
- Rational Quality Manager/Common and Repository
- Rational Team Concert/APT and SCM
- Rational Team Concert/Work Items and Build
- Rational Quality Manager/Work Items
- Rational Quality Manager/Quality Management
- Jazz Team Server/Requirements
- Jazz Team Server/Star
It is not clear to me if the option "Run all data warehouse collection jobs for all applications" starts a partial load or a full load.
Thanks!
Accepted answer
Hello Andre,
if you are using the Default CLM data collection jobs the full load can only be triggered manually job by job.
The execution order is the one you mentioned.
DCC and Data Magager ETL offers a possibility for run the full load for all applications as a batch.
Best Regards,
Francesco Chiossi
if you are using the Default CLM data collection jobs the full load can only be triggered manually job by job.
The execution order is the one you mentioned.
DCC and Data Magager ETL offers a possibility for run the full load for all applications as a batch.
Best Regards,
Francesco Chiossi
Comments
Andre Gusmao
Feb 12 '15, 12:08 p.m.I forgot to mention that I was hoping the upgrade to 5.0.2 could solve this, since there are some migration jobs that will run before the actual partial load jobs. But it didn't change anything.