Java ETL jobs execution history still show history even though it was disabled and moved to DCC
RTC 5.0.1/5.0.2 used.
The users moved to DCC at the end of Oct in 2014 and disabled the java etl jobs following the step 6 in
[https://hub.jazz.net/clmhelp/index.jsp?re=1&topic=/com.ibm.rational.dcc.doc/topics/t_roadmap_dcc.html&scope=null]
to clear the java etl jobs. However, they still notice that the java etl job history show the job execution(successful) from time to time. It does not seem all jobs are run every time. Up to the end of last year, SCM, Build, Common and APT, workitems jobs were executed sometimes. Workitem job can run up to more than 1 day or more than 10 hours.
Then in this year, workitem jobs are no longer seen but SCM/Build/Common/APT still run and it is not at regular base, for example, there are entries for today and last run was back to 3/Feb 2015 etc.
Does anyone see this behavior? I am wondering what could trigger this odd behavior?
The users moved to DCC at the end of Oct in 2014 and disabled the java etl jobs following the step 6 in
[https://hub.jazz.net/clmhelp/index.jsp?re=1&topic=/com.ibm.rational.dcc.doc/topics/t_roadmap_dcc.html&scope=null]
to clear the java etl jobs. However, they still notice that the java etl job history show the job execution(successful) from time to time. It does not seem all jobs are run every time. Up to the end of last year, SCM, Build, Common and APT, workitems jobs were executed sometimes. Workitem job can run up to more than 1 day or more than 10 hours.
Then in this year, workitem jobs are no longer seen but SCM/Build/Common/APT still run and it is not at regular base, for example, there are entries for today and last run was back to 3/Feb 2015 etc.
Does anyone see this behavior? I am wondering what could trigger this odd behavior?
Accepted answer
Hello Don,
all the types of ETL (CLM Data Collection Jobs, Data Manager ETL and DCC) write the outcome of the job executions to the config.etl_info table of the data warehouse.
So even if the CLM Data Collection Jobs is disabled you will still see entries in the CLM Data Collection Jobs still being executed, despite the fact that they are disabled, you can check the [application]-etl.log files in CLM and check if there was any activity.
Best Regards,
Francesco Chiossi
all the types of ETL (CLM Data Collection Jobs, Data Manager ETL and DCC) write the outcome of the job executions to the config.etl_info table of the data warehouse.
So even if the CLM Data Collection Jobs is disabled you will still see entries in the CLM Data Collection Jobs still being executed, despite the fact that they are disabled, you can check the [application]-etl.log files in CLM and check if there was any activity.
Best Regards,
Francesco Chiossi
Comments
1 vote