RCR 2.0GA fails in ETL BuildRecord job

One thing you can do is look at the source data in RQM and see if you can make it compliant, since that looks to be the problem.

In RQM, go to Builds -> View Build Records.
Try to go through you Build Records, checking that the "State" is set on each, and that it is a value available in the drop-down.

Hope that helps.
Regards,
John

Anyone else seeing this? We're running RCR on Windows / SQL Server 2005, with the DB server separate from the report/ETL server, against RQM 2.0. Upon kicking off the RQMAll dataMovementTask, the job fails. Browsing on the server into <installdir>\Rational Insight\cognos\datamanager\log shows the failure in the BuildRecord job:

Data Manager v8.4.27.78 -- Copyright (C) 2008 Cognos ULC, an IBM Company. All rights reserved.
COGNOS INTERNAL USE ONLY
databuild -- start run on <machinename> (23-Sep-2009 16:03:54)

Run context:
JobStream 'RQMAll'
JobStream 'RQM_ODS'
Build 'BuildRecord'

Build 'BuildRecord' - run id 1, audit id 16
Fact Build 'BuildRecord'
Parsing Reference Definition
Validating Build Specification

DM-STM-0270 The script specified for the derived data source item 'STATE' of the data source 'DataSource1' of the DataStream 'Untitled' is not valid. The derived data source item or result column name 'status' does not exist in the data source.

Build 'BuildRecord' Failed
databuild -- failed (23-Sep-2009 16:03:59)

We've tried rebuilding the data warehouse metrics from RQM, creating new project areas, trying project areas with data converted from RQM 1.0.1.1, all to no avail -- every job crashes at this point.

Is anyone successfully using RCR on Windows / SQL Server?

Hi John,

Actually, at the time the report was run, there were no build records in the candidate project. I tried creating one, and setting its state to a valid state, but no success - still get the same error.

ri_jdbc and ri_odbc logs both show no error so I'm indeed quite puzzled.

I now have a Jazz work item open on this and an IBM PMR, and will update back here if/when the problem is resolved.