Report query parsing problem

I didn't find any report of this problem...
Using APEX 3.0.1.00.07, I have a report of type "SQL Query (PL/SQL function body returning SQL query)" with the "Use Generic Column Names (parse query at runtime only)" radio button selected.
When the region source contains the string "ORDER BY" in any form that I've tried (even in a comment), attempting to save the region fails with "Your query can't include an "ORDER BY" clause when having column heading sorting enabled."
I do indeed have column sorting enabled on certain columns, but I don't see how that is relevant under these circumstances since the query produced at runtime does not have an ORDER BY clause.
Am I overlooking something or is this a parsing problem?
Rodney

Rodney,
It's just checking for order by being included in your query, and if so and you have column heading sorting enabled, it's raising this error because you can't have both (even if it's commented out).
Regards,
Marc

Similar Messages

Performance problem with report query

Hi,
I am encountering a performance issue with a page returning a report.
I have a page that has a region which joins 2 tables. One table has about 220,00 rows, while the other contains roughly 60,000 rows. In the region source of the report region, the query includes join condition with local variables. For example, the page is page 70, and some join conditions are:
and a.id=:P70_ID
and a.name like :P70_NAME
I run the query that returns a large number of rows from sqlplus, and it takes less than 30 sec to complete.
When I run the page, the report took about 3 minutes to return.
In this case, :P70_NAME is initialized to '%' on the page.
I then tried to substitute variable value directly in the query:
and a.id=1000
and a.name like '%'
this time the report returned in about 30 sec.
I then tried another thing which specified the region as "PL/SQL Function returning sql query", and modified the region as follows:
l_sql := '.......';
l_sql := l_sql || 'and a.id=' || v('P70_ID')
and similar substituting :P70_NAME to v('P70_NAME') and append its value to the l_sql string.
The report query page also returned in 30 sec.
Is there any known performance issue with using the bind variable (:PXX_XXX) in the report region?

If you are able.. flush the shared_pool, run your
report then query the v$sql_area or v$sql_text tables.
Or do a google query and look up Cary Milsap's piece on enabling extended trace .. there is your sure fire way of finding the problem sql. I am still learning htmldb but is there a way to alter session enable trace in some pre-query block?

Printable Report Query Problem

I am attempting to develop a printable report query. I have created a report query under shared components that consists of 12 separate queries that gather data that all relates to a single page item. The intent is to create a printed PDF document for the user on demand that will display all this information about the page item that they have selected.
The report query gathers the information and generates an XML file in the following format.
<DOCUMENT>
    <ROWSET1>
        <ROWSET1_ROW>
                         *Data from query 1*
        </ROWSET1_ROW>
    </ROWSET1>
    <ROWSET2>
        <ROWSET2_ROW>
                          *Data from query 2*
        </ROWSET2_ROW>
        <ROWSET2_ROW>
                          * Data from query 2*
        </ROWSET2_ROW>
   </ROWSET2>
   <ROWSET3>
       <ROWSET3_ROW>
                          * Data from query 3*
       </ROWSET3_ROW>
       <ROWSET3_ROW>
                          * Data from query 3*
       </ROWSET3_ROW>
   </ROWSET3>
</DOCUMENT>I then took this XML file and developed an RTF template using BI Publisher desktop and imported it as a Report Layout.
I then connected this RTF layout to the report query and ran it. I did not get the all the data to print.
I found the reason it did not work was that the XML file that is generated from the report query is not static. The next XML file that was generated from the report query looked like this:
<DOCUMENT>
    <ROWSET1>
        <ROWSET1_ROW>
                           * Data from query 3*
        </ROWSET1_ROW>
        <ROWSET1_ROW>
                           * Data from query 3*
        </ROWSET1_ROW>
    </ROWSET1>
    <ROWSET2>
        <ROWSET2_ROW>
                           * Data from query 7*
        </ROWSET2_ROW>
        <ROWSET2_ROW>
                           * Data from query 7*
        </ROWSET2_ROW>
        <ROWSET2_ROW>
                           * Data from query 7*
        </ROWSET2_ROW>
   </ROWSET2>
   <ROWSET3>
       <ROWSET3_ROW>
                           * Data from query 1*
       </ROWSET3_ROW>
   </ROWSET3>
</DOCUMENT>So I cannot develop an RTF template to display the data if I do not know where that data will appear in the generated XML.....
Questions (I will offer several POINTS to anyone who can answer any of these questions!!!!)
I am using APEX version 3.1
*1. Why does the report query seem to randomly renumber and reorder the XML data it produces?*
*2. Is there any way to make the report query output the XML data in the same order that the individual queries are ordered every time?*
*3. Is there any way to specifically name the rowsets or rowset rows that is supported by APEX?*
*4. Are there any other methods that I can explore to produce this report?*
*5. Is this a problem because I am on an old release? Is this not a problem on 4.1?*
Edited by: bhenderson on Feb 1, 2012 8:22 AM

Thanks for your response.
There are 12 separate queries in the report query. Each one is in a separate box on the report queries screen.
I don't know how to post an image here, but I will try to describe it:
The first query selects several fields relating to :P5_WIP_ENTITY_ID, which is a Work order. This query is header information about the job and should only return one row.
The other queries get other information relating to :P5_WIP_ENTITY_ID, like part numbers that may have been issued to that job, purchases made for that job and so on. These queries may return more than one row or may not return anything.
I have created the queries in the order that I want them to display on the form, however, when the XML is generated, ROWSET1 may have the data from the Header Query one time, then the next time it may have data from the purchase query. In other words, it does not display the data in the order that the queries appear on the report query page, and it seems to reorder the output at random.
I have looked everywhere I could think of, but there doesn't seem to be any way of connecting or relating the separate queries. I also tried doing separate queries in one box and joining them, but there is a limit of 60 data items you can select from one query box.
Edited by: bhenderson on Feb 3, 2012 10:01 AM

Recurring problem - need to touch report query to make page to work again

Hello
In my APEX 3.0 (Oracle 10.2.0.3.0) application I have a main menu which is a very simple page with one report that selects from a local table (no dblink) what pages the logged user has access to.
The problem is that now and then (around once a week) users get "page not found" after they log in to the application but before the main menu is displayed. After some testing I found out that, to fix it, I need to touch the report query (let's say, adding an extra space somewhere) and apply changes. After that, the page works fine...
I have other much more complex pages in the application that don't have such problem.
Any advice? Where should I start investigating to fix this?
Thanks
Luis
PS: From the error_log file:
[Mon Aug 20 10:12:54 2007] [error] [client 10.0.10.87] [ecid: 11877561:10.0.24.16:14092:0:37471,0] mod_plsql: /pls/apex/f HTTP-404 ORA-03113: end-of-file o
n communication channel\n
[Mon Aug 20 10:12:54 2007] [alert] [client 10.0.10.87] [ecid: 11877561:10.0.24.16:14092:0:37471,0] mod_plsql: Unable to reset state for mode 0: Err 3114 url=>/pls/apex/f

i have this exact same problem in our production environment
i really need help to fix it or we'll lose our major client
they're fed up with it
anyone?

Problem with Report Query

I have tested the integration of Apex3.0 and BI Publisher via Report Query.
This works very well, however I want to create a hierarchical XML document via the following Query:
select a.id,
a.persoonsnr,
a.volgnr_dvb,
a.jaar,
a.naam,
a.code_sagitta,
a.status,
a.invgebruiker,
a.invdatum,
a.mutgebruiker,
a.mutdatum,
cursor (
select w.afspraken
from hri_opmwerkresult w) as owr
from hri_prsactiviteiten a
I get the error message ORA-00932 inconsistent datatypes expected number got curser
Is there a work around to create a report-query with master-detail info?

Anyone?

How to change report query dynamically in Oracle APEX?

Hi,
I want to dynamically change the where condition in APEX report query. Can anyone help me solve my this problem?
(Just want to change the query which we change in Oracle Reports using lexical parameter to change &Where, &Order by etc. dynamically!!)
Thanks, Praful

Hi
I've been using flexible queries in APEX for a few years now, and your question just added a whole new dimension to the flexible and powerful nature or writing reports in APEX.
While APEX Interactive reporting has almost completely removed the need the equivalent of Lexicals in Oracle Reports, I thought it might be fun to try and use lexicals in an APEX report.
Before we start I should summarise the powerful capability of APEX reporting to have oprtional parameters (lots and lots of them if this is needed).
For each parameter, you simply add a page item which will hold the value of the parameter.
The item/parameter can be populated by typing in the value, defining an LOV, using a date-picker etc.
To make the parameter optional simply use an OR in the where clause.
So for a apge item P200_PARAM1.....include
WHERE (:P200_PARAM1 IS NULL
OR COLUMN1 = :P200_PARAM1)
This way you can either leave the page item null or type in / select a value from a LOV.
There is a small quirk in APEX LOV's which sometimes returns a value of '%' or '%null%' - depending on the version - when no value is selected.
See Patrick Wolf's solution for this at Re: Null value handling in LOVs
I include this Application Process in all my APEX applications ;)
Now let's look at using the equivalent of Oracle Reports Lexicals......
First-off - this is based on the APEX SQL report - NOT Interactive Report.
It relies on the fact that you can let the query be parsed only at runtime.
1. Define an SQL report entering the 'core' of your query.
With a query like SELECT ENAME, JOB FROM EMP
Select 'Generic Columns' option in the 'Column Headings' section
Finish the report creation
2. Define a page item - say P200_LEXICAL - type text on the page
3. Edit the report and update the SQL query to include your lexical page item
SELECT ENAME, JOB FROM EMP &P200_LEXICAL. (REMEMBER THE '.' AT THE END)
Ensure that the option "Use Generic Column Names (parse query at runtime only)" is selected at the bottom of the query
4. Add a button to the page -using 'Create a button displayed among this region's items' the will submit the page.
5. Run the page - you will see all the employee names and job desdriptions
6. Enter a where clause into the 'Lexical' textbox - say "WHERE ENAME LIKE 'K%'" and click the 'Go' button
Voila! your where clause is magically applied.
Try any variant you like adding an ORDER BY clause etc...... this is FUN!
7. Clear the value of the LEXICAL and click go.
Edit the report and move the &P200_LEXICAL. into the selected columns (or add another one)
SELECT ENAME, JOB &P200_LEXICAL. FROM EMP
8. Run the page
Enter ",SAL" in the textbox and "Go"
We can add as many columns as we like (subject to the "Maximum number of generic report columns:" set below the SQL query in the report edit section)
Now because we have all the flexibility in APEX of setting page items using SQL or PLSQL you can set the value of the lexical programatically, or just pre-set a few values in an LOV - the options are limitless.
While I've never had the need to use lexicals - you can see that APEX provides the most Flexible Lexicals in town.
Eat your heart out "Oracle Reports"!!!
Have fun
Mike

Using a function in a report query

Why can't I call a function (basically a query) in a report query like I can from from SQL?
Consider the following:
Select MyFunctionName(arg) from dual;
From SQL, it works great! No problem:
In a report query, [Application/Shared Components/Report Queries] It doesn't work. I get an XML error:
XML Parsing Error: not well formed
<MyFunctionName('arg')><?xml version="1.0"?>
----------------------^
Why?
Looks like APEX is not even executing the function...
See I have a table with a CLOB field that contains properly formatted HTML. I cannot simply query for that content, since Oracle escapes the tags in the conversion to XML. I have to (somehow) tell Oracle to keep it's grubby mitts off my CLOB content. As far as I can tell, using DBMS_XMLGEN.setConvertSpecialChars is the only way to keep Oracle from escaping the html stored in the table--in fact, the DBMS_XMLGEN documentation states that it why this functionality exists in the first place!
This is why I am trying to use a function. Simply queries don't work. The function I wrote works beautifully in SQL, but not in a report query...
Edited by: Vorlon on Aug 5, 2010 1:20 PM

Note from the first post:
"In a report query, [Application/Shared Components/Report Queries]" Let me clarify: This report query is used in a BI Publisher report. Getting the information to the screen isn't the problem. I have that working. :-) It's just when I try to get the report to print that I see APEX has escaped the output before reaching BI Publisher--so BI Publisher is not the issue. I have a xsl template that will process the embedded HTML, but APEX is escaping my data before I can act on it. In other words:
It seems Apex is not creating the XML properly, since it escapes everything. Even when the function passes back data correctly.
Has anyone else seen this? Ideas for a workaround?
Thanks!

Post upgrade to 3.1 issues : Unable to open report query

Hi,
We have upgraded our APEX version from 3.0 to 3.1. We have some wierd problems now
1. I tried to add a new column link to an existing report region and I get an error.
failed to parse SQL query:
ORA-00911: invalid character
2. I have to make some changes to an existing report query and I am unable to open it. I Get the following error:
ORA-01461: can bind a LONG value only for insert into a LONG column
Can anybody let me know the reason for these errors.
Thanks
Knut

Hi Scott,
We created a test case on apex.oracle.com in my workspace (DGIELIS_31)
It's Application 54025, the query is called "Test Big Query".
Currently it works, but edit the query and copy one of the comment lines and paste it in to take it over 4k. You should get the same error.
Just for the record:
- in APEX 3.0 in a non UTF-8 (WE8ISO8859P15) database this query was working
- When migrating to UTF-8 database with APEX 3.1.1 we can't open the queries.
- We can't use a view in this case, it's a pretty complex query which already uses MV's and the tables in questions are pretty huge. The query we had to come up with is pretty big to get optimal performance.
If you want I can email you my login details or create you a user.
Regards,
Dimitri
-- http://dgielis.blogspot.com/
-- http://www.apex-evangelists.com/
-- http://www.apexblogs.info/

Performance issues when creating a Report / Query in Discoverer

Hi forum,
Hope you are can help, it involves a performance issues when creating a Report / Query.
I have a Discoverer Report that currently takes less than 5 seconds to run. After I add a condition to bring back Batch Status that = Posted we cancelled the query after reaching 20 minutes as this is way too long. If I remove the condition the query time goes back to less than 5 seconds.
Please see attached the SQL Inspector Plan:
Before Condition
SELECT STATEMENT
SORT GROUP BY
VIEW SYS
SORT GROUP BY
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID GL.GL_CODE_COMBINATIONS
AND-EQUAL
INDEX RANGE SCAN GL.GL_CODE_COMBINATIONS_N2
INDEX RANGE SCAN GL.GL_CODE_COMBINATIONS_N1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUES_N1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUE_SETS
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUE_SETS_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES_TL
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUES_TL_U1
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUE_NORM_HIER_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_LINES
INDEX RANGE SCAN GL.GL_JE_LINES_N1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
TABLE ACCESS BY INDEX ROWID GL.GL_JE_HEADERS
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_DAILY_CONVERSION_TYPES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_SOURCES_TL
INDEX UNIQUE SCAN GL.GL_JE_SOURCES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_CATEGORIES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
INDEX UNIQUE SCAN GL.GL_BUDGET_VERSIONS_U1
INDEX UNIQUE SCAN GL.GL_ENCUMBRANCE_TYPES_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
TABLE ACCESS BY INDEX ROWID GL.GL_JE_BATCHES
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_PERIODS
INDEX RANGE SCAN GL.GL_PERIODS_U1
After Condition
SELECT STATEMENT
SORT GROUP BY
VIEW SYS
SORT GROUP BY
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
TABLE ACCESS FULL GL.GL_JE_BATCHES
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_HEADERS
INDEX RANGE SCAN GL.GL_JE_HEADERS_N1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
INDEX UNIQUE SCAN GL.GL_ENCUMBRANCE_TYPES_U1
INDEX UNIQUE SCAN GL.GL_DAILY_CONVERSION_TYPES_U1
INDEX UNIQUE SCAN GL.GL_BUDGET_VERSIONS_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_SOURCES_TL
INDEX UNIQUE SCAN GL.GL_JE_SOURCES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_CATEGORIES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_LINES
INDEX RANGE SCAN GL.GL_JE_LINES_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
TABLE ACCESS BY INDEX ROWID GL.GL_CODE_COMBINATIONS
INDEX UNIQUE SCAN GL.GL_CODE_COMBINATIONS_U1
TABLE ACCESS BY INDEX ROWID GL.GL_PERIODS
INDEX RANGE SCAN GL.GL_PERIODS_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUES_N1
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUE_NORM_HIER_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES_TL
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUES_TL_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUE_SETS
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUE_SETS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
Is there anything i can do in Discoverer Desktop / Administration to avoid this problem.
Many thanks,
Lance

Hi Rod,
I've tried the condition (Batch Status||'' = 'Posted') as you suggested, but the qeury time is still over 20 mins. To test i changed it to (Batch Status||'' = 'Unposted') and the query was returned within seconds again.
Ive been doing some more digging and have found the database view that is linked to the Journal Batches folder. See below.
I think the problem is with the column using DECODE. When querying the column in TOAD the value of P is returned. But in discoverer the condition is done on the value Posted. Im not too sure how DECODE works, but think this could be the causing some sort of issue with Full Table Scans. How do we get around this?
Lance
DECODE( JOURNAL_BATCH1.STATUS,
'+', 'Unable to validate or create CTA',
'+*', 'Was unable to validate or create CTA',
'-','Invalid or inactive rounding differences account in journal entry',
'-*', 'Modified invalid or inactive rounding differences account in journal entry',
'<', 'Showing sequence assignment failure',
'<*', 'Was showing sequence assignment failure',
'>', 'Showing cutoff rule violation',
'>*', 'Was showing cutoff rule violation',
'A', 'Journal batch failed funds reservation',
'A*', 'Journal batch previously failed funds reservation',
'AU', 'Showing batch with unopened period',
'B', 'Showing batch control total violation',
'B*', 'Was showing batch control total violation',
'BF', 'Showing batch with frozen or inactive budget',
'BU', 'Showing batch with unopened budget year',
'C', 'Showing unopened reporting period',
'C*', 'Was showing unopened reporting period',
'D', 'Selected for posting to an unopened period',
'D*', 'Was selected for posting to an unopened period',
'E', 'Showing no journal entries for this batch',
'E*', 'Was showing no journal entries for this batch',
'EU', 'Showing batch with unopened encumbrance year',
'F', 'Showing unopened reporting encumbrance year',
'F*', 'Was showing unopened reporting encumbrance year',
'G', 'Showing journal entry with invalid or inactive suspense account',
'G*', 'Was showing journal entry with invalid or inactive suspense account',
'H', 'Showing encumbrance journal entry with invalid or inactive reserve account',
'H*', 'Was showing encumbrance journal entry with invalid or inactive reserve account',
'I', 'In the process of being posted',
'J', 'Showing journal control total violation',
'J*', 'Was showing journal control total violation',
'K', 'Showing unbalanced intercompany journal entry',
'K*', 'Was showing unbalanced intercompany journal entry',
'L', 'Showing unbalanced journal entry by account category',
'L*', 'Was showing unbalanced journal entry by account category',
'M', 'Showing multiple problems preventing posting of batch',
'M*', 'Was showing multiple problems preventing posting of batch',
'N', 'Journal produced error during intercompany balance processing',
'N*', 'Journal produced error during intercompany balance processing',
'O', 'Unable to convert amounts into reporting currency',
'O*', 'Was unable to convert amounts into reporting currency',
'P', 'Posted',
'Q', 'Showing untaxed journal entry',
'Q*', 'Was showing untaxed journal entry',
'R', 'Showing unbalanced encumbrance entry without reserve account',
'R*', 'Was showing unbalanced encumbrance entry without reserve account',
'S', 'Already selected for posting',
'T', 'Showing invalid period and conversion information for this batch',
'T*', 'Was showing invalid period and conversion information for this batch',
'U', 'Unposted',
'V', 'Journal batch is unapproved',
'V*', 'Journal batch was unapproved',
'W', 'Showing an encumbrance journal entry with no encumbrance type',
'W*', 'Was showing an encumbrance journal entry with no encumbrance type',
'X', 'Showing an unbalanced journal entry but suspense not allowed',
'X*', 'Was showing an unbalanced journal entry but suspense not allowed',
'Z', 'Showing invalid journal entry lines or no journal entry lines',
'Z*', 'Was showing invalid journal entry lines or no journal entry lines', NULL ),

Report query with bind variable

Trying to create a report query for xsl-fo print. For output format I pick "derive from item" then pick the item name from the list, on the next screen, I paste the query with the bind variable. on the next step test query, I always get "data not found" regardless what value I type in. This is the same query that I ran under sql commands without any issues.
Does anyone run into the same issue as I have when attempted to create a query with bind var ? There is no problem creating a query without bind varibles. . thanks.
Munshar

Hi, please did you get any solution to this issue? I am having similar challenge right now.
select     EMP.DEPTNO as DEPTNO,
     DEPT.DNAME as DNAME,
     EMP.EMPNO as EMPNO,
     EMP.ENAME as ENAME,
     EMP.JOB as JOB,
     EMP.MGR as MGR,
     EMP.HIREDATE as HIREDATE,
     EMP.SAL as SAL
from     SCOTT.DEPT DEPT,
     SCOTT.EMP EMP
where EMP.DEPTNO=DEPT.DEPTNO
and      DEPT.DNAME =upper(:dname)
This run perfectly in sql developer, toad, and even inside publisher if I login directly to publisher to create report.
Generating this same query in shared component query builder and testing it returns no data found. If I remove the last line, it works. but with the last line, it return no data found. It seems no one has been able to provide solution to this issue

Bind Variables and Shared Component Report Query

I have a query in a region report which I have replicated to a shared component report query.
Both queries reference page items as bind variables in the where clause.
The report region on screen shows the correct results but the report query shows "no data". This is the case when running "Test Query" and "Download XML data" from the shared component report query definition. If I hardcode the variable names I get rows returned, If I use bind variables - and specify the values for these variables I get no data. THe XML file contains the tags for each bind variable I have specified but has no data between the tags. I have Ticked the box to include application and session state but it appears that the bind variables are not being used.
When I use my report query in the application (URL tied to a button) I get the same problem, the binds are not being passed to the report query.
Can someone please clarify if this is a bug or not? And if not, how can I get it to work.
I am using Apex 4.0.2
Thanks
Kathryn

Hi
To confirm, yes I selected the bind variables. I used these in the report layout, but the xml file has them as empty i.e.
<P0_START_DATE><P0_START_DATE/> with nothing in between.
IN the Test Query section, if I put real values in the boxes for the bind variables, I get no data found. If I hardcode the values into the query, I get the data.
I've repeated the create report query many times and have created a report layout in RTF. I can use the layout with my region - in the print attributes and the layout works with the query but I need to create a PDF using 2 queries - ROWSET1 and ROWSET2. I can generate the XML but the values in the rows are all empty. When I use the layout with a report query instead of the region, I get no data even though I have used the same sql and have selected the bind variables. I was using variables from page items on page zero but have also tried using page items on the current page, the result is the same.
I need to use a report query and a report layout as I need data from 2 queries in the PDF.
I looked at your demo - what happens if you add a second sql query to the report query - is there any chance I can look at the back end (developer access?)
Thanks for your input
Kathryn

Report Query returning "No Data Found" with bind variables

I put a simple query into Report Query:
Select "bluefish". "name" as "name",
"bluefish"."primary_flag" as "primary_flag",
"bluefish"."status" as "status",
"bluefish"."ID" as "ID" from "bluefish" "bluefish" where "bluefish"."ID" = :P3_XPRINTID
When I test the query, data is returned; however, when I try to run the query using "Test Report" button, I get an error 01403 No Data Found. If I replace the bind variable with an explicit value, the report works.
Anyone have any ideas as to what is causing this problem? I am using the Generic Report Layout, with various output types. I AM editting the query and defining the bind variable before I test the report (otherwise, the query wouldn't run).
Charles

Sometimes if you create a form/report/whatever using the wizards, it will create an After Submit process called something like Reset Page - basically you want to make sure you don't have any After Submit processes that call a Clear Session state (it may say something like Clear Cache for Page).
In your branch, there is also a box that says Clear Cache - you want to make sure that does not have page Number 8 in it or it will clear your session state.
Put the page in Debug mode and read through it - check to make sure your value is getting saved and maybe you can see what is going wrong.

Report region with column link that opens a pdf doc based on report query

Hello
I'm building a report table that displays info about a customer - simple select - and, for each record, has associated column links based on report queries that receive ID as parameter. When clicked, it opens the report in pdf extension. My problem here is how to pass the ID as a parameter to that report query considering i'm using a report table and that there are no items in page 71...
This is the report query i'm using:
select initcap(a.customer) customer
, initcap(a.address) address
, initcap(a.rep) rep
, (select initcap(b.city)
from portal_records b
where b.contrib=a.contrib
and b.year=to_char(sysdate,'yyyy')) city
, (to_char(a.datereg,'dd')||' de '||to_char(a.datereg,'Month')||' de '||to_char(a.datereg,'yyyy')) datereg
from portal_authorizations_cve a
where a.id=:P71_ID ???????????????
I thank in advance all your replies!!

Hello
First of all, let me compliment your for your demo application... It's awesome!
I've looked into your sample (page 15) and, as far as i see, it opens a document saved in a table's column. I don't want the file to be saved there but generated when the user clicks on that particular link... So i still have the problem of how to pass the right ID as a parameter considering there is no page item on that page...
My javascript knowledge is little so i ask you: when clicking the link, is there any way of opening a window with the url f?p=&APP_ID.:0:&SESSION.:PRINT_REPORT=Authorization_CVE and the ID as a parameter?
I thank in advance!

Setting a bind variable in a Shared Component Report Query

I have defined a Shared Component Report Query in APEX using a bind variable similar to below
Select name, id , ....
from asset
where id = :id
I have also created a Report Region that displays a table where one of the columns contains a value I would like to be a link column that can launch the Report Query and pass its value to the bind parameter :id in the report query. This in turn would generate a pdf report for the details associated with that column. I am having problems setting the :id bind parameter. How do I do this?
Can anyone help?
Thanks

The bind values are set from session state. So if try something like this:
Select name, id , ....
from asset
where id = :P1_ID
With P1_ID being a page item, for which you set the session state / value before generating the PDF file. So assuming you already have a page with a report and a page item, and that page item is already used in your report, then you could just create a button to download the PDF, make sure the button is a submit button, and create a branch pointing to the report query URL (or in 3.1 use the create button wizard, to do this declaratively.)
Regards,
Marc

What is the best practice for running a long report/query against an active database?

We are using SQL Server 2012 EE but currently do not have the option to run queries on a R/O mirror though that is my long term goal. I am concerned I may still run into the below issue in that scenario as well since the mirror would also be updating data I
am querying.
I have a view that joins across several tables from two databases and is used by an invoicing program on existing data. Three of these tables are also actively updated by ongoing transactions. Running a report that used this view did not use to be a problem
but now our database is getting larger and we have run into some timeout problems for the live transactions coming in.
First the report query was timing out so I set command timeout to 0 and reran the query which pegged all 4 CPUs 100% for 90 minutes and so I finally killed it. Strangely there were no problems with active transactions during that time so I'm wondering if the
query was really running doing anything useful or somehow spinning and waiting. I reviewed the view and found a field I was joining on that was not indexed so created an index on that field, reran the report, which then finished in three minutes and all the
CPUs were busy but not at all pegged out. Same data queried both times. I figured problem solved. Of course later, my boss ran a similar invoice report, with the same amount of data, and our live transactions started timing out 100% while his query was running.
I did not get a chance to see the CPU usage during that time.
I looked at the execution plan of the underlying view and added the suggested index but that did not help. When I run the just the view at SQL Server it does not seem to cause any problems and finished in a couple seconds. Perhaps something else going on in
the reporting tool using the view.
My main question is - Given I have to use the live and active database, what is the proper way to run a long R/O query/report so that active transactions can still continue to update
tables that I am querying? sp_who2 did show transactions being blocked so I guess a long query accessing the tables blocks live transactions accessing those same tables, but certainly I'm not the only one doing this. I
am considering adding "with (nolock)" but am hoping there is a better standard practice as that clause can return dirty data and I understand why. Thx, Dave
Thanks, Dave
Dave

Hello
You can change the DB isolation level to Read uncommitted
http://technet.microsoft.com/en-us/library/ms378149(v=sql.110).aspx
or use WITH (NOLOCK)
I do use NOLOCK option for the dirty reads to avoid locks on the tables
Javier Villegas |
@javier_vill | http://sql-javier-villegas.blogspot.com/
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

Report query parsing problem

Similar Messages

Maybe you are looking for