Data Collection jobs are failing on RTC,JTS and QM
1.In JTS- Star is succeeding but Common is failing
2.In RTC and RQM all files are failing.
- The following error is seen in the application server log:2012-03-28 00:08:27,885 [ccm0009001: AsynchronousTaskRunner-3] ERROR
- ervice.internal.common.CommonRemoteSnapshotService - 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.
- 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.
I asked LDAP team, they replied-
The logs are full of the account not able to authenticate because it has been locked out due to too many bad passwords. Therefore I can assume the invalid password error you are getting is because you are using the wrong password.
Also, the account "UserID" does not have any access to the ldap server (FDS) other than to authenticate itself, which you can only do if you supply the correct password.
I am not getting how to proceed further and mske the job run successful.Please help me!!
Accepted answer
Hi Raj,
Have you checked to make sure that the user ID you are using for the ETL user has the "Data Collector" license and that you can log in to the application with that ID? If the ID is being locked due to invalid credentials, it sounds like the ID/password need to be updated in the data collection jobs page for each application (ie - <application>/admin -> Reports -> Data Collection Jobs). These jobs run at midnight every night by default, so if one of the applications is is configured with an invalid password I can see the ID being locked. I would start by first confirming that the ID is not locked, the ID is able to authenticate to your LDAP server, and that all passwords are updated with the right values. Hope it helps,
Have you checked to make sure that the user ID you are using for the ETL user has the "Data Collector" license and that you can log in to the application with that ID? If the ID is being locked due to invalid credentials, it sounds like the ID/password need to be updated in the data collection jobs page for each application (ie - <application>/admin -> Reports -> Data Collection Jobs). These jobs run at midnight every night by default, so if one of the applications is is configured with an invalid password I can see the ID being locked. I would start by first confirming that the ID is not locked, the ID is able to authenticate to your LDAP server, and that all passwords are updated with the right values. Hope it helps,