REP-0496: Internal Error - Unable to Parse The Query.

[JOPA]

I am using Reports 2.5 and I am finding much, I repeat, a lot of difficulty with a column.



Well, after giving a breath after query more or less above I made several tests and the results are a success - as expected .

I went to Reports, I created a query, I put the query above and I was surprised by the message below:

Rep-0496: Internal Error - Unable to Parse The Query.
Cause: The SQL Statement that You Have Entered Cannot Be Parsed Because IT Contains An error.

Action: Review The SQL Statement That You Entered And En Enredient That You Are Using The Correct Syntax. For more information, See The Oracle7 Server SQL Language Reference Manual.

Please help me.

[victorhugomuniz]

Well ..

Every time I used Report I did query via procedure and then from my report I call the procedure ..

I'vê never seen use Query Direct

[JOPA]

Like this? I did not understand.

I am in Data Model> Queries

I put this query in a new query (object) to use the results of each column in the report.

But, I am surprised by this error.

[victorhugomuniz]

Then ..

My Data Model I put a proced call that has Query I want to execute ..

Create parameters in my report and use in this call

[JOPA]

Well,

I'm green yet, but come on.
You get the query and create a Program Units procedure with that query, is that it?
How is this code-line call, as an example?

The bank is 8i and Reports is 2.5.

[SergioLBJr]

Checks if you are not using a feature that the version of your Reports does not support.

[JOPA]

I see here.
... Studying SQL / 92 and SQL / 86.

I still continue with the problem.

[SergioLBJr]

Do you have any latest version of Report to test this query ??

If not, start trying to take some of the functions that you are using aí, until query works and then looks for a way to get around what is causing the problem.

[dr_gori]

Look at the "About" to see the version of your SQL and PLSQL and then compare with the bank version.
Probably in the bank works because it is a much newer version, that is, it allows you to do NVL with a SELECT in.

já Reports 2.5 Probably does not support that kind of thing.

A possible solution:
* Create a package that populates a table with your SELECT. Dai in reports, just do select * from temp ...

leaves work to the bank, did you? hehe

[JOPA]

Unfortunately I'm hostage from this version.

All application reports were created in this release.

I'm working on Query still seeking to eliminate this problem.

grateful for attention, any new information will be welcome.

[JOPA]

Only as information:

Select all

About 
 
Reports 2.5.7.0.4 
ORACLE7 Server Release 7.3.4.1.0 
Oracle Procedure Builder 1.5.6.15.10 
Oracle PL/SQL V1.2.1.11 - Production 
Oracle CORE Version 3.5.4.0.0 
Oracle Tools Integration Services 1.2.0.5.0 
Oracle Tools Commom Area 2.0.0.9.0 
Oracle Toolkit 2 for Windows 32-bit platforms 2.3.6.19.0 
Resource Object Store 2.2.2.2.0 
Oracle Help 2.1.5.4.1 
Oracle Virtual graphics System 2.1.11.0 
Oracle Image 2.0.7.9.0 
Oracle Multimedia Widget 2.0.7.9.0 
Oracle Tools GUI Utilities 1.2.0.10.0

[Marciel]

Quemys problematic as this can be used more easily if you create a view. In your report, call the view rather than your query. This will also take better performance, since the view runs on the server, and not locally as it would be query.

Embrace

[JOPA]

Dear,

by virtue of many demands, complexity and change of specification
of the business rule, I finished for these days and ended up forgetting
reiterate here.

My solution was to refine the data to the maximum, which will be displayed in the
report in Forms. This involves Miscellaneous Program Units with some
calls to bank procedures, functions, dblinks, triggers, .... aff -
beat of things. I created a "temporary" table so that when invoking the
report, this make a simple query in this table listing your data.

At last, the end.

Thank you all for your attention - Thank you!