8.2 Reports failing in 8.3

[cognoise8]

Hello Cognos gurus,
     We recently migrated from 8.2 to 8.3 and have been getting this error ever since(we tested the same thing in 8.2 and it still works fine but just doesnt work in 8.3)

Basically what is happening is,when we create a simple list report with only one column in a particular query subject it fails(gives the below error) whereas when we use all the columns in that query subject in that report it runs fine,this is the error we are getting in 8.3

QE-DEF-0469 QE Message
RQP-DEF-0588 A many to many relationship is found in the join path involving query subjects

UDA-QOS-0006 Error
UDA-SQL-0107 A general exception has occurred during the operation "prepare".
ORA-00918: column ambiguously defined

QE-DEF-0459 CCLException
RQP-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-9'.
UDA-SQL-0107 A general exception has occurred during the operation "prepare".
ORA-00918: column ambiguously defined

RSV-VAL-0004 Unable to find query information for the item Account ID.

    The same Report works fine in Cognos 8.2 .  Also when we use the all the columns in the query subject the report run fine, but if we select only one column(happens for all the columns in that query) the report fails to run and give the above error.

Have any of you faced any similar issues after migrating from 8.2 to 8.3 .
   It looks like some of the joins that were working in 8.2 are no longer working in 8.3. Does anyone know if any of the joins/cardinality supported in 8.2 are no longer supported  in 8.3.

[blom0344]

From what I heard Cognos has taken a step to correct report writers. Once a query item is not used in a report it is supposedly deleted from the query....?
We had issues with crosstab reports that we only managed to get working again by working in an object in the report and hiding it from view.

Check SQL generated between the 8.2 and 8.3 versions..

[cognoise8]

    Thanks for the reply blom.I have included all the query items in query in the report but still the same error exists.
The problem seems to be caused due to the join structure..we had a few outer joins in the model but they still worked in 8.2 but are no longer working after we migrated the model to 8.3( when we test the query subjet with the outer joins the test fails).So I was thinking has anything changed with respect the way join structures (or the supported joins) in 8.3

[blom0344]

To answer that question you should take the generated SQL (Cognos type) and run it through a compare (ultraedit, notepad++) This should quickly give you an an idea where the Cognos plan may have changed.
We have not observed any changes in join behavior AFAIK..

[vij]

Hi cognoise8 ,

even i was stuck with the below mentioned error ....
RSV-VAL-0004 Unable to find query information for the item Account ID.

for this error i follow the below steps....
1)In properties pane go to that particular List to which u have assigned the Query which contains Account ID.
2)In properties pane in DATA select Properties
3)tick the chech box for Account ID data item
now it will not give u the "RSV-VAL-0004......" error


hope it will help u
thnnks,
vij
:)

[JGirl]

I would also check the Govenor settings in your FM model as these may have changed during the upgrade.

[cognoise8]

Thanks for the response guys....
Blom..we are unable to generate any sql for this case in 8.3 as it fails to validate and unable to generate sql..anyother way to get the sql..without doing a trace?
Vij..I tried that out..didnt help in our case
JGirl...yeah we did compare the governor settings of 8.2 and 8.3.. and made sure they were the same.

thanks again guys

any more ideas :)

[rockytopmark]

Remove one query item at a time until you get success, then trace back the culprit to the model, through the model and back to the database... you must have something that is modeled wrong. 

[vij]

hi

then assign the same query to the whole page and follow the steps as given below....
1)In properties pane in DATA select Properties
2)tick the chech box for Account ID data item

might help u ....

vij
:)

[Phoebe]

Remove one query item at a time until you get success, then trace back the culprit to the model, through the model and back to the database... you must have something that is modeled wrong.

This is the correct answer, worked for me!  In my case it was a query calculation item that was causing it.