Data source adapter error: java.sql.SQLSyntaxErrorException: ORA-00904

[pakhi]

Hi Team. We published package in DQM mode in Cognos 10.2.2 portal. JDBC is already enabled in the data source. We migrated reports from Cognos 10.2.1 to Cognos 10.2.2 but few reports are not working after migration. The error message is common in all the failed report:

Data source adapter error: java.sql.SQLSyntaxErrorException: ORA-00904: "from$_subquery$_005"."coulmn_name": invalid identifier

These reports are working fine in old version 10.2.1 with CQM mode but not working in new version 10.2.2 with DQM mode.

Please let us know if anyone has any clue on this issue.

[MFGF]

Hi Team. We published package in DQM mode in Cognos 10.2.2 portal. JDBC is already enabled in the data source. We migrated reports from Cognos 10.2.1 to Cognos 10.2.2 but few reports are not working after migration. The error message is common in all the failed report:

Data source adapter error: java.sql.SQLSyntaxErrorException: ORA-00904: "from$_subquery$_005"."coulmn_name": invalid identifier

These reports are working fine in old version 10.2.1 with CQM mode but not working in new version 10.2.2 with DQM mode.

Please let us know if anyone has any clue on this issue.

The error looks like it's saying an invalid identifier or alias is being used? Are the affected reports using the same query subject? Do they have anything funky going on with joined queries? Any hard-coded SQL? Anything that you can identify that is common between them?

MF.

[pakhi]

Thanks for your reply. Actually I came to know about one thing during my investigation. There is one particular dimension if we include that dimension in the query then report started giving error from Cognos. This dimension is present in all the failed reports. But if we execute same report query directly in data base then it works fine. Any idea what exactly DQM mode may make impact on the same?

[MFGF]

Thanks for your reply. Actually I came to know about one thing during my investigation. There is one particular dimension if we include that dimension in the query then report started giving error from Cognos. This dimension is present in all the failed reports. But if we execute same report query directly in data base then it works fine. Any idea what exactly DQM mode may make impact on the same?

I'd be looking at how that dimension is defined in your framework. I'm guessing you will find something unusual in its definition...

MF.