Problems with requirements after upgrading to RQM 2.0.0.1

Hi,
having recently upgraded to RQM 2.0.0.1, I am now having problems
viewing any requirements linked to a test plan (Planning -> View
Test Plans -> Plan Name -> Requirements). I see the following
error pop up:

CRJAZ1037I Failing query -> WorkItemQueryModel r =
WorkItemQueryModel.ROOT; AstQuery q = (AstQuery)
IItemQuery.FACTORY.newInstance(r);
q.filter(r.workItemType()._eq("requirement")._and(r.itemId()._inLargeList)));

From the reports generated though, it is clear that the requirements
are actually still attached as before, and when I view the
requirements individually, they are still showing as linked to the
test plan.

Has anyone else seen this? Is there a solution to this problem?

Sounds like you are using DB2 and did not do the last state of the

rjhannah wrote:

Hi,
having recently upgraded to RQM 2.0.0.1, I am now having problems
viewing any requirements linked to a test plan (Planning -> View
Test Plans -> Plan Name -> Requirements). I see the following
error pop up:

CRJAZ1037I Failing query -> WorkItemQueryModel r =
WorkItemQueryModel.ROOT; AstQuery q = (AstQuery)
IItemQuery.FACTORY.newInstance(r);
q.filter(r.workItemType()._eq("requirement")._and(r.itemId()._inLargeList)));

From the reports generated though, it is clear that the requirements
are actually still attached as before, and when I view the
requirements individually, they are still showing as linked to the
test plan.

Has anyone else seen this? Is there a solution to this problem?

Sounds like you are using DB2 and did not do the last state of the

dmehaffywrote:
rjhannah wrote:
Hi,
having recently upgraded to RQM 2.0.0.1, I am now having problems
viewing any requirements linked to a test plan (Planning -> View
Test Plans -> Plan Name -> Requirements). I see the following
error pop up:

CRJAZ1037I Failing query -> WorkItemQueryModel r =
WorkItemQueryModel.ROOT; AstQuery q = (AstQuery)
IItemQuery.FACTORY.newInstance(r);

q.filter(r.workItemType()._eq("requirement")._and(r.itemId()._inLargeList)));
From the reports generated though, it is clear that the
requirements
are actually still attached as before, and when I view the
requirements individually, they are still showing as linked to the
test plan.

Has anyone else seen this? Is there a solution to this problem?

Sounds like you are using DB2 and did not do the last state of the
upgrade process. You need to create a new TMPSPACE table in DB2.
Look
near the bottom of the upgrade tab in the all downloads section. That

is the type of error you will see if you don't add the
table.