Rational Insight bind error when execute ETL
![]()
Hi
I installed a Rational Insight 1.1.1.7 and when started running the ETL jobs it fails, after tracing back through the logs I found that the problem is on RTC_WorkitemState4.0.5, and this is shown on log: #################### Run context: JobStream 'CLM6.0.1_All' JobStream 'RTC_ODS6.0.1_DeltaLoad' JobStream 'RTC_ODS6.0.1' JobStream 'RTC_Workitem6.0.1' JobStream 'RTC_WorkitemDimensions5.0' Build 'RTC_WorkitemState4.0.5' [PROGRESS - 04:34:06] Fact Build 'RTC_WorkitemState4.0.5' [PROGRESS - 04:34:06] Parsing Reference Definition [PROGRESS - 04:34:06] Validating Build Specification [PROGRESS - 04:34:09] Checking Fact Data existence [PROGRESS - 04:34:10] Processing Reference Data [PROGRESS - 04:34:10] Processing Dimension Domains [PROGRESS - 04:34:10] Processing Fact Data DM-DBM-3662 A bind error occurred on parameter 2; the value is too large (length 43 vs 40). [PROGRESS - 04:34:10] Build 'RTC_WorkitemState4.0.5' Failed databuild -- failed (29-Apr-2016 04:34:10) ######################## I've found this technote http://www-01.ibm.com/support/docview.wss?uid=swg1PM78304 with is the same issue apparently but on RRC, however I'm not sure how to implement the solution they provided, since I don't know which database table needs to be modified or what values and how on xdc files. Can you please advice? Regards |
One answer
![]()
This should be a defect as well. You should contact Support and mention PM78304, so a new defect can be submitted.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
The RTC_WorkitemState4.0.5 ETL build updates two tables in the warehouse (RIODS.REQUEST_STATE and RIODS.REQUEST_STATUS). The only field in those tables that is 40 characters in length is EXTERNAL_KEY2. The error is stating that an row to update into those tables has an EXTERNAL_KEY2 length that is 43 characters, when the field is 40 characters. In this case I don't think you want to increase the EXTERNAL_KEY2 field to 43 characters in the warehouse. EXTERNAL_KEY2 should never be more than 40 characters. I have seen this error before on EXTERNAL_KEY2 and it was a bug in Rational Insight that was later fixed. As a temporary solution I added the following filter to the Fact delivery: Length(EXTERNAL_KEY2) <= 40.