Data Collection Job Status fails
12 answers
The best place to start looking is in the ETL logs. These should be located in the server install directory in the logs folder (ie - C:\IBM\JazzTeamServer\server\logs). You should see the following logs:
ccm-etl.log for CCM
qm-et.log for QM
jts-etl.log for JTS and RM
You can also run the ISALite Data Collector and provide it in your PMR by going to C:\IBM\JazzTeamServer\support\ISALite and running "runISALite.bat" which will collect all the logs from the server as well as some other helpful information for support. Hope it helps,
Comments
Thanks. I'll look there. Anything in particular that I should look for?
Unfortunately our RTC is installed on a closed network and the output of the runISALite batch file produces a ton of files that makes it practically impossible to get those files off the network and to IBM without going through a lengthy extraction process (classification).
Comments
Not Seeing User ID. I have a screenshot but an unable to upload at this time.
"sorry, file uploading requires reputation >60"
Is there some other way to get the file to you?
If I select the Data Warehouse Connection, I do see some configurations settings like Data Collection User or Consumer key. But this field is not changeable.
Comments
It was set to JTS. I changed it to Form and now on the Data Collection Jobs screen the field indicates User ID and Password but it's still showing the consumer key not the User ID.
Is the ETL user the same as the Data Collection User that's shown on the Warehouse Connections screen or should it be the User who is trying to run the reports?
Is the Warehouse Connection user (ADMIN) the account that automatically runs the Jobs everyday as opposed to the user who manually runs the jobs on demand?
Comments
Okay. I changed the User ID to my login User ID and the jobs are now running. The first few have already passed.
How is this supposed to work in real life? Will I have to run the jobs whenever the user needs reports or is there some way to allow users to run the jobs themselves?
We only have one Data Collector license.
In any case, Thank you very much for your support.
You can re-configure the time they run by entering an integer value under Reports -> Data Warehouse Connection -> Data Warehouse Snapshot Time, but midnight (off hours) is best (as it does put some stress on the applications), unless you have some scheduled maintenance that you know will interfere with the job (ie - database goes down at midnight for some maintenance task).
I'm glad the jobs are running now!
Comments
So the jobs will run automatically at midnight? Do i need to set the account that it uses or is that controlled automatically by RTC?
Can the ID be reset to one of the 'dummy' user IDs ? (e.g. ccm_user) We just moved to 4.0.1 and our dw jobs (in ccm ) are failing with "peer not authenticated". The ID being used doesn't have any collector license and it's an LDAP ID that we've setup for lots of other purposes. Having its password in lots of places makes me twitchy (not for security, but just the possibility of overlooking if the password should ever be reset).
TIA -- Kevin
I would advise against using one of the other functional users (ie - ccm_user) as the ETL user. Those users are dedicated to other tasks and should not be designated for other activities.