Intermittent RQM connectivity errors during ETL

I'm running Insight 1.0.1 with iFix1, and reporting against several RTC repositories and RQM projects. Twice this week during my scheduled ETL I've had an intermittent failure in the RQM ETL, at different points... once at 'TestCase_Workitem_Lookup' and the other in 'Reservation', but both gave the same error message:

DM-DBM-0402 UDA driver reported the following:

UDA-SQL-0031 Unable to access the "Rational Quality Manager" database.

UDA-SQL-0107 A general exception has occurred during the operation "attach".

DM-DBM-0306 UDA driver error connecting to 'Rational Quality Manager'.

I've confirmed the database is still available and not being backed up or anything like that, and it only seems to happen intermittently. Are there suggestions on how to further debug what's going on here?
You need to report this issue with RQM. The log is merely stating that it can not communicate with the RQM REST service so it's not the RQM database that is failling.

Hello.
Please create a defect for RQM on jazz.net attaching the ri_jdbc.log
that you find in the <etl>\log directory. If the job was
scheduled you find it in C:\WINDOWS\system32\config\systemprofile\logs
and equivalent dirs for other OS'. Also let us know the rough time and
date when the error happened.

Thanks,
Peter.



On 8/19/2011 8:38 AM, petroula wrote:

jmw2wrote:
I'm running Insight 1.0.1 with iFix1, and reporting against several
RTC repositories and RQM projects. Twice this week during my
scheduled ETL I've had an intermittent failure in the RQM ETL, at
different points... once at 'TestCase_Workitem_Lookup' and the other
in 'Reservation', but both gave the same error message:


DM-DBM-0402 UDA driver reported the following:

UDA-SQL-0031 Unable to access the "Rational Quality
Manager" database.

UDA-SQL-0107 A general exception has occurred during the operation
"attach".

DM-DBM-0306 UDA driver error connecting to 'Rational Quality
Manager'.


I've confirmed the database is still available and not being backed up
or anything like that, and it only seems to happen intermittently.
Are there suggestions on how to further debug what's going on
here?

You need to report this issue with RQM. The log is merely stating
that it can not communicate with the RQM REST service so it's not the
RQM database that is failling.