Problem with ETL job scheduling
![]()
“Data Warehouse Snapshot time” property is 12.
But it does not run at 12:00, it runs next at 10:20.
The timezone on server is correct.
What could be wrong?
Thanks!
|
Accepted answer
![]()
Hello Tayane,
if you need to run the ETL multiple times a day, you can consider the new Data Collection Component (DCC). Note: this requires CLM 5.X. For details see: Data collection with Data Collection Component http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.1/com.ibm.rational.dcc.doc/topics/c_ovr_process_etl_rrdi.html Best Regards, Francesco Chiossi Tayane Fernandes selected this answer as the correct answer
|
9 other answers
![]()
I have observed that the start time of some DW jobs has crept forward. For example the (in)famous Star job on the JTS can run anywhere from 3-10 hours on one of our setups. The overall start hour is 24, but see this:
[ inverse sorted with respect to Reports / DW Job Status ] Status Job Start Time End Time DurationI don't see any real consistency beyond the first couple of jobs, e.g. WHY does Requirements start @ 7A, Star start time varies wildly and is creeping into our "primetime" use. |
![]()
Hi Francesco!
But I have just Rational Team Concert and yet my jobs are like:
|
![]()
Hello Tayane,
even if you only have RTC installed, the schedule of the ETL is controlled by JTS. You should check https://server:port/jts/admin > Reports > Data Collection Jobs and see the value set for Job Scheduling > Start Time. See: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m6/topic/com.ibm.rational.reporting.admin.doc/topics/t_running_the_data_collection_jobs.html#etl_start_time Best Regards, Francesco Chiossi |
![]()
Hello Francesco,
The Start Time is already 12 too.
But jts jobs also run at 10:20 and 22:20
|
![]()
Hello Tayane,
this is a very good point, if your server is using the Brazil time, on Sun Feb 16th the clock moved back 1 hour, correct (as far as I have found it's the only country ending DST on the Third Sunday February)? This is a bit less than the schedule difference that you are seeing but is consistent with the change, assuming that the server counts 12 hours between each ETL run. 16 Feb 00:00 + 12h schedule -1 for DST end = 17 Feb 11:00 There are still 45 minutes unaccounted for, but given the coincidence with the dates I think this could definitely be related to the DST end. It's possible that if the ETL schedule is not a full day, it could keeps counting the intervals in order to accommodate schedules that doesn't fit a full day. I think that after the next server restart the ETL should get back to the schedule you configured. Best Regards, Francesco Chiossi |
![]()
At a meeting with engineering staff, they told me that when I run the jobs twice a day, I can not set a schedule to run it.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.