Is there a way to run the WI data collection job independent of (i.e. offline to) the JTS ?
Our WI job run for days, it last failed on Jun 18th, after running for 7 days, 22 hrs; since, various scheduled maintenance, physical host crashes, and JTS crashes had prevented any successful WI job. The last good WI job was on June 9th.
We just wonder if we ever catch up with a good WI job.
Is there any way to run (and update the Warehouse) the WI job by itself or together with the full collection, independent of any JTS interruption ?
Or is there a way to "save & continue" so we can restart the WI job after a JTS interruption ?
We are on CLM 4.0.3 without RQM, and do not use RTC Source Control nor Build.
One answer
You seem like a good candidate for the new DCC feature. Depending on what version you are on, it may be better to move to DCC, which eliminates a lot of bottlenecks found in typical Java ETL performance. You can search the information center for "Data Collection Component" and review the documentation (note this is available in 5.0).
Comments
Thx Stephanie for the DCC feature. Unfortunately the DCC is introduced with 5.0.1 (or is it 5.0), and our upgrade policy prevent us from jumping to last release 5.0 from our scheduled mid-Sep upgrade to 4.0.6. It looks like our PMR will result in a hotfix:Defect: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=322143 (for a method that fetches states added since a given time).
Comments
Lily Wang
Jul 08 '14, 2:12 a.m.As I known, the recovery checkpoints for ETL feature has been introduced in RTC 4.0.1. Please see https://jazz.net/downloads/rational-team-concert/releases/4.0.1?p=news#checkpoint.
long TRUONG
Jul 08 '14, 8:25 p.m.Thx for the tip Lily. We do have a long running [PMR 53034,49R,000], which is still open, for the slowness of the WI collection job. SWAT will advise us if we should submit a separate PMR for the failed WI job.