RM Requirement ETL job fails with column EXTERNAL_KEY2 too large with CLM 4.0.7
The Data Manager ETL job RM4.0.3Requirement fails with the error:
The Modification date for this row is 2014-01-14 3:25:21 PM, so it should not be coming in, as the modifiedsince date in the query is '2014-08-07 19:27:04'. The following is the query:
|
One answer
Benjamin Silverman (4.1k●6●10)
| answered Aug 08 '14, 3:54 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
We shouldn't be loading rm/preferences resources in to the DW. It sounds like there is something wrong with a reference in RDNG that makes the ETL think this resource needs to be loaded. When you run the query directly from Data Manager, does this resource come back? If so, is it the only resource that has a URL value containing rm/preferences?
Comments See comment on this in the thread above.
Benjamin Silverman
commented Aug 11 '14, 9:54 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd suggest contacting support to investigate. I'm not aware of any changes in 4.0.7 that would cause this behavior, but perhaps support will be able to reproduce this behavior.
|
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
There are 77 resources with a URL value containing "rm/preferences". There are also many other unusual resources such as bookmarks, wrappedResources and locks and all with a blank name.
The ETL ran successfully Friday night, with just 22 resources read in since the last run at '2014-08-07 19:27:04'.
The ETL has failed since then, using a modifiedsince date of '2014-08-09 07:57:08', and rather than get just 10-20 new resources it is getting 3969 resources with includes the preference resources with the long guid which causes the ETL to fail.
If I run the SQL command in SQL Term I will get 3969 resource rows with a modifiedsince date of '2014-08-09 07:57:08' and 17 resource rows with a modifiedsince date of '2014-08-07 19:27:04'. The '2014-08-09 07:57:08' datetime should get less than 17 rows, not the 3969.
This only start happening on the CLM Server that was upgraded to 4.0.7 on Thursday Aug. 7. We have 5 other CLM Server, two at 4.0.4 and three at 4.0.6 which have had no problems. All are planned to be upgraded to 4.0.7 over the next several weeks.
All 6 CLM Servers have been upgraded to 4.0.7 and the ETL is running Rational Insight 1.1.1.3.
I still get the error: "'EXTERNAL_KEY2'; the value is too large (length 55 vs 40)". As a workaround I added "AND Length(EXTERNAL_KEY2) <= 40" to the Filters for the RRC ETL jobs RM4.0.3Requirement and RM4.0.3RequirementStg.
With this workaround I no longer get the fatal error, but the RM4.0.3Requirement and RM4.0.3RequirementStg jobs read in way more requeirement records than they should. As well several other RM jobs that do not use the 'EXTERNAL_KEY2' and so don't have the key length error, do have the problem of reading in more data than they should and taking much longer than they should. Examples are RM4.0.3RequirementStg, RM4.0.3StgLinks and RM4.0.3StgReq.
Prior to CLM 4.0.7 the RM jobs for the 6 CLM servers took 6 minutes, 1 minute for each CLM Server. With 4.0.7 it now takes 50 minutes to 70 minutes for the 6 CLM Servers.