It's all about the answers!

Ask a question

Insight1.1.1: F_REQUEST_TPLN_AGING build fails


0
1
Ruslan Luchnikov (3121311) | asked Jun 03 '13, 5:54 a.m.
Hi, all
After execution of the JobStream CLM4.0.1_All, I have found error in the execution log of the build 'F_REQUEST_TPLN_AGING':

[EXECUTEDSQ - 00:36:33] data insert

insert into "RIDW"."F_C_REQUEST_TPLN_AGING" ("TOTAL_REQUESTS", "DATE_ID", "PROJECT_ID", "ITERATION_ID", "COMPONENT_ID", "RESOURCE_ID", "STATE_MIN", "STATE_MAX", "STATE_TOTAL_DAYS", "STATE_ID", "REQUEST_CLASS_ID", "SEVERITY_ID", "PRIORITY_ID", "REQUEST_TYPE_ID", "TESTPLAN_ID", "AGING_METRIC_ID", "REC_DATETIME", "CREATOR_ID") values (:p1, :p2, :p3, :p4, :p5, :p6, :p7, :p8, :p9, :p10, :p11, :p12, :p13, :p14, :p15, :p16, :p17, :p18)


DM-DBM-0365 A bind error occurred on column 'ITERATION_ID'; attempt to bind a NULL value to a non-nullable column.

DM-DLV-0101 Delivery 'F_C_REQUEST_AGING': failed on statement "INSERT INTO "RIDW"."F_C_REQUEST_TPLN_AGING" ("TOTAL_REQUESTS", "DATE_ID", "PROJECT_ID", "ITERATION_ID", "COMPONENT_ID", "RESOURCE_ID", "STATE_MIN", "STATE_MAX", "STATE_TOTAL_DAYS", "STATE_ID", "REQUEST_CLASS_ID", "SEVERITY_ID", "PRIORITY_ID", "REQUEST_TYPE_ID", "TESTPLAN_ID", "AGING_METRIC_ID", "REC_DATETIME", "CREATOR_ID") VALUES (1, -1, 31, NULL, -1, 614, 0, 0, 0, -1, 7, 174, 125, 138, -1, 1, '2013-06-01 00:35:44', 614)".

DM-BLD-0005 The delivery 'F_C_REQUEST_AGING' failed.

[PROGRESS   - 00:36:33] Build 'F_REQUEST_TPLN_AGING' Failed


But jobstreams Facts  and Build_Star succeed.
How to fix this problem or it is not serious?
Thanks

2 answers



permanent link
wei zhang (2011) | answered Jun 06 '13, 12:12 a.m.
JAZZ DEVELOPER
The directly cause is ITERATION_ID is NULL when insert into table, but it table don't accept null data from this column.
Please follow these steps to find root cause:
Query all requests from RIODS.REQUEST table with filter CREATOR_ID=614, TESTPLAN_ID=-1, REQUEST_TYPE_ID=138, PRIORITY_ID=125, SEVERITY_ID=174, REQUEST_CLASS_ID=7 and so on. The filter will be contains all dimensions, not only above.

Then check ITERATION_ID from result set, and query related things RIODS.ITERATION and RIDW.D_ITERATION table. With all this data and your RQM data source, please double check data consistent to find root cause.

permanent link
Ruslan Luchnikov (3121311) | answered Jun 07 '13, 7:34 a.m.
Hi, wei
I'am trying to write this query, but  in RIODS.REQUEST don't have column TESTPLAN_ID. Column TESTPLAN_ID there are in table riods.request_testplan_lookup,but it's empty.  And when I trying to launch query with filter "iteration_id is null"  for tables REQUEST and ITERATION,  i didn't find null data.  Maybe insert is  incorrect?

Your answer


Register or to post 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.