why if using RI I must disable the data collection jobs (ETL) of the CLM applications?
I found this info in the IBM Help:
If you upgrade to Rational® Insight 1.0.1.1 and use the Data Manager data collection feature of Rational Insight, you must disable the data collection jobs of the CLM applications.
My system is organized in 6 databases: I_CCM, I_ETL, I_DW, I_RRC, I_QM, I_JTS: which databases are updated by the DM ETL jobs and which ones are updated by CLM ETL jobs ? which database is used by the RQM Built-in BIRT reports ?
If you upgrade to Rational® Insight 1.0.1.1 and use the Data Manager data collection feature of Rational Insight, you must disable the data collection jobs of the CLM applications.
My system is organized in 6 databases: I_CCM, I_ETL, I_DW, I_RRC, I_QM, I_JTS: which databases are updated by the DM ETL jobs and which ones are updated by CLM ETL jobs ? which database is used by the RQM Built-in BIRT reports ?
Accepted answer
All the etls that feed into the data warehouse that is being upgraded need to be disabled during the upgrade process. This is to ensure that no etls are running while the data warehouse DB is being upgraded. In short all etls feed the data warehouse DB, so they all need to be disabled.
Once the upgrade is completed, then re-enable the etls.
Once the upgrade is completed, then re-enable the etls.
4 other answers
BOth etls:
1) Feed into the same data warehouse DB
2) Basicly do the same thing
) Running both could cause conflicts
The advantage of running the Insight ets is that they run on the insight jvm, isolated from the CLM jvms. If the CLM etls are run, they will run on the same jvms as CLm and use up resources that could otherwise be used for other CLM activities.
1) Feed into the same data warehouse DB
2) Basicly do the same thing
) Running both could cause conflicts
The advantage of running the Insight ets is that they run on the insight jvm, isolated from the CLM jvms. If the CLM etls are run, they will run on the same jvms as CLm and use up resources that could otherwise be used for other CLM activities.
Comments
OK, that could be the reason, if both were scheduled to run at the same time.
Now, can you tell me why (I have both sets of ETL jobs running) and still I do not have the right data in the RQM report (trend execution) and I need to run the RQM ETLs manually in addition almost every day since a week ? Is all data in I_ETL or or I_DW or I_QM ?
i do not believe it matters when the insight etls or CLM etls run. If they both run, there is potential for conflicts.
If the star jobs are completing successfully and the data appears to be missing information, then please open a PMR to engage support.
If the star jobs are completing successfully and the data appears to be missing information, then please open a PMR to engage support.
You actually need the main RQM job to successfully complete as well as the Star job. The main RQM job will populate the operational data store (ODS) section of the data warehouse with a snapshot of the most recent data. Once that has completed, the Star job uses the ODS data to calculate its metrics, so if you don't have both jobs completing successfully some of your metrics may be incorrect, such as your execution trends.
Comments
Does the sequence matter ? I see the QM job (QM Job for my PA) run short after midnight, while I see the star job, configured in RI run at 2 am. In the morning I then have to run teh QM job again otherwise the old snapshot does not contain all data.
Yes - the QM job should run first. Otherwise the ODS will not be populated correctly for the Star job to gather the metrics.