It's all about the answers!

Ask a question

RIODS.PROJECT table not populating with Insight ETLs

June Boston (1941537) | asked Jul 17 '14, 11:43 a.m.

The Rational Insight ETL does not appear to populate a table it uses in the data warehouse, RIODS.PROJECT.  This table is referenced by the db-incrementing PROJECT_ID value from tables such as RIODS.REQUEST, but REQUEST just uses -1 as the Project ID for any new project's work items.  The RIODS.PROJECT table binds that to project name "Others" and has no other data.

The JKE Banking projects show up just fine, but any new projects are not being put into this table.  We're digging into the ELTs now to see why this is, but if anyone could enlighten us that would be great.

Thank you,
June Boston

2 answers

permanent link
Francesco Chiossi (5.7k1719) | answered Jul 17 '14, 11:58 a.m.
Hello June,

RIODS.Project is populated by the JFS_ProjectArea build of the JFS job.
You can maybe start by checking the logs for that build and see that the jfsXXX.xdc file is properly configured with the connection details to RTC for the JFS_CCM resource.

Best Regards,

Francesco Chiossi

June Boston commented Jul 17 '14, 12:11 p.m. | edited Jul 17 '14, 12:17 p.m.

We've found that job (in the ODS > JazzFoundationServices> JFS3.0.1 directory) by drilling down through the ETLs.  The job's query is run with {$RESOURCEGROUP} being used to identify the table to query in question, and I would think it is passed JFS, JFS_CCM, and JFS_QM as it already has data on the sample lifecycle app and all the related projects.  If we run the query and pass it JFS_CCM it shows the new project, but somehow this is not inserted into the target table RIODS.PROJECT still.

We are wondering how the WHERE modifiedsince='{$MODIFIED_SINCE}' functionality works, since that might be filtering things out.

permanent link
June Boston (1941537) | answered Jul 17 '14, 5:19 p.m.
 Our OOTBE2E top level job was not calling the JFS jobs; we failed to re-add them when creating the Delta OOTB job.

We have added the JFS job first in the job queue for the OOTBE2E job and our table is populating correctly.

Francesco Chiossi commented Jul 18 '14, 5:39 a.m.

Glad to hear that it's fixed.
Thanks for sharing the solution.

Your answer

Register or to post your answer.