Report DMS-E-SS_SYNTAX error after upgrade

[dabrattom]

Hi,

I'm currently upgrading a report from Impromptu 6.2 to Impromptu 7.0. Everything worked well with V6.2.

When opening the report with IMPR 7.0, i get the following error:
'DMS-E-SS_SYNTAX, A syntax error was detected near ')''.

The SQL code generated by the 7.0 version is very complex and does'nt work in SQL*PLUS. It fails on "XSUM" statements which don't appear in 6.2 version.

I'm using:
Impromptu 7.0 Build No 716.2-0
Oracle Client 8.1.7.0.0
Oracle Server 8.1.7.4.1

Cognos support told me to add "use automatic ORACLE Decode=0" in IMPROMPTU.ini. It changes nothing....

I searched everywhere on the web and i didn't found any case like this one. An user from this forum had this kind of error which has disappeared after reinstalling Impromptu. I did the same but without success.

Thanks in advance.
Dabratt.

 

[griffindm]

dabrattom,

The XSUM function appears in Cognos pseudoSQL, which is normally generated when the report is not connected to the database. It is extremely unusual to see this produced when a catalog is connected to the database.

The option to turn off automatic Decode can be useful in avoiding overly complex decode statements from the automated translation of If-Then-Else statements in calculated columns. Another alternative is to manually replace these with simpler decode statements yourself. This can greatly reduce the complexity of the generated SQL.

When I get this type of error (i.e. not immediately obvious in its cause) what I generally do is to 'deconstruct' the report, taking off layers of complexity until I can determine which additional layer of calculations is causing the problem (i.e. what was the last thing removed before it started working again). This can prove invaluable in finding a way to remedy the situation.

Hope this helps a little.

Dave Griffin


The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
Want good answers? Read FAQ20-2863 first!

http://www.decisionsupportgroup.com

 

[dabrattom]

thanx for your answer Dave.

Well... i have 'reconstructed' the whole report in Impromptu V7. When i keep the same structure, i always get the error.

But i finally resolved it by specifying some associations that weren't specified in the original report... and it worked!