The lone License ETL data collection job would require the Common job in CLM 4.0.3 but not in 4.0.6: common.exception.ETLException CRRRE1404E ?
We are scheduled to upgrade RTC/RRC from 4.0.3 to 4.0.6 this Fri, with TEST env already in 4.0.6. We have had issues with slow (Java) ETLs with the WI job, without any prospect of a hotfix for the same fix planned for 5.0.1.
So we had decided to turn all ETLs data collection jobs off (until we upgrade to 5.0.1 when we can rely on the Java ETL fix, or the new DCC), however we need the License usage in our reports, so we turn the lone License ETL job back on, in both env, TEST and PRD. To our amazement:
- It started almost right away (long before the set start time for ETL jobs) on TEST (4.0.6) like a charm
- with successful builds reported in the jts-etl.log, which has no records of the common job, while there is nothing going to the ccm-etl.log, where records for the common job would have been gathered if it is running.
- But on PRD (which get a day head start), we kept on checking without seing and data collected, every build was unsuccessful, with
- java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
- in the jts-etl.log
- While still nothing went to the ccm-etl.log, where common job records would have been collected for a running common job.
- Is it really far fetched to think that on 4.0.3, the License job would requires an actively running common job, while on 4.0.6 it has been streamlined for the License job to work alone on its own ?
2 answers
Hi long,
Here are my answers to your comments/questions:
- The License ETL starts long before the set start time for ETL jobs: The License ETL is set to run every hour.
- Relationship between the Common ETL and the License ETL: None, they can run independently.
- jts-etl.log file gets updated while ccm-etl.log does not: The License ETL is a JTS ETL, it's expected to only run in the JTS, therefore only the jts-etl.log file will get updated.
Regarding the AuthenticationException, what authentication type are you using? Have you verified that the User/Consumer Key and Password/Consumer Secret are correct and belong to a user that has assigned a Data Collection license? If you activate any other JTS ETL in the production environment, would that one run successfully using the same credentials used by the License ETL?
Thank you,
Clara
Here are my answers to your comments/questions:
- The License ETL starts long before the set start time for ETL jobs: The License ETL is set to run every hour.
- Relationship between the Common ETL and the License ETL: None, they can run independently.
- jts-etl.log file gets updated while ccm-etl.log does not: The License ETL is a JTS ETL, it's expected to only run in the JTS, therefore only the jts-etl.log file will get updated.
Regarding the AuthenticationException, what authentication type are you using? Have you verified that the User/Consumer Key and Password/Consumer Secret are correct and belong to a user that has assigned a Data Collection license? If you activate any other JTS ETL in the production environment, would that one run successfully using the same credentials used by the License ETL?
Thank you,
Clara
Comments
Author below. All ETLs jobs were turned on, running OK except the WI job too slow then kept failing after running 10, 11 days. PMR got to a fix planned for 5.0.1 but no hotfix for any 4.0.x. We decided to turn all ETL jobs off.
Then need license collection, turned lone license job on. The same sequence done on both TEST and PRD. on TEST it was done after upgrade to 4.0.6, and lic job running OK. on TEST was done on 4.0.3, not working, persist up to now 4 days after upgrade to 4.06.
last sentence should read:
... on TEST it was done after upgrade to 4.0.6, and lic job running OK. on PRD was done on 4.0.3, not working, persist up to now 4 days after upgrade to 4.0.6.
Comments
long TRUONG
Sep 14 '14, 11:00 p.m.NO! It was not a question of versions. PRD is now upgraded to 4.0.6, the issue persists, the lone license job keeps failing ...