Rational Insight Data Movement Task fails for Focal Point job
Environment: Windows Server 2008 R2, SQL Server 2008 R2, Rational Insight 1.1.1.2
All jobs are scheduled and are working except for the Focal Point job. This was working without any problems until last week when it stopped running abruptly. There is no error message in the ri_jdbc.log file either. In Insight, I get the following error:
DM-DBM-0400 UDA driver reported the following on connection FocalPoint: UDA-SQL-0107 A general exception has occurred during the operation "prepare". CRRRE9000E: Internal Java error, check ri_jdbc.log for details
However, if I run the job from Data Manager, there is no problem. Not sure what could be causing this. Nothing has changed in our environment either. Any thought/ ideas?
5 answers
Hello Kunal,
good to hear that a republishing fixed it.
Usually the Internal Java error means that something went wrong with the XML ODBC Driver.
That's why it mentions to check for ri_jdbc.log.
If there are no errors there maybe the XML ODBC Driver process just died.
You might want to check if the connection sequence in the driver is complete at the time of the error (comparing with one from a working instance) or what was the last action in the log.
When you publish a job there are some catalog information that are passed over, so changes in the ETL or the configuration of the ODBC sources might sometime require a republishing.
If no such changes occurred, it's definitely strange that the job suddenly started to fail.
Best Regards,
Francesco Chiossi
good to hear that a republishing fixed it.
Usually the Internal Java error means that something went wrong with the XML ODBC Driver.
That's why it mentions to check for ri_jdbc.log.
If there are no errors there maybe the XML ODBC Driver process just died.
You might want to check if the connection sequence in the driver is complete at the time of the error (comparing with one from a working instance) or what was the last action in the log.
When you publish a job there are some catalog information that are passed over, so changes in the ETL or the configuration of the ODBC sources might sometime require a republishing.
If no such changes occurred, it's definitely strange that the job suddenly started to fail.
Best Regards,
Francesco Chiossi