32k Rowsize Limit (ORA-006502) for Report Query Shared Objects in Apex 4.1

We're trying to move legacy reports off of PlanetPress into Apex. One of the report queries has over 20 tables and attempting to run with the "Test Report" button in the Edit Report Query screen gets the error message:
Error ORA-06502: PL/SQL: numeric or value error: character string buffer too small
This problem appears to have been characterized previously here:
Listener Error - character string buffer too small (ORA-06502)
If I comment out 13 lines/items in my SELECT clause, the Test Report runs okay. If I add back in an innocuous literal sellect of a 100-character string, it goes back to the 6502 error.
I was trying to add more literal strings to force APEX to shift internally from a 32k-limit to a CLOB for the row, however, with a 32k literal string in my SQL statement, APEX crashes. I can't strip out columns from my SQL as all are needed for the report.
I would very much appreciate a work-around or a patch to Apex 4.1 to address this limitation. Thank you.

Try moving some of your select logic into a view, thus you can select from the views and reduce your code... (Move the joining between tables and such to the view..)
Thank you,
Tony Miller
Webster, TX

Similar Messages

  • How use parameters on a html region for report query region

    Hi all.
    I have created a number of report regions which initially query some data.
    The requeriment now is to have a date range (initial and final) and use this range as a parameter for report queries.
    i created a new region containing these two date values. Now i need to:
    - Give this date fields and initial value: say first and last day of current month.
    - Perform a validation to ensure initial date is less or equal to final date.
    - And most importantly, i need to reexecute the queries based on this date range.
    How do i do it...?
    Thanks in advance ...!

    Start here http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21679/toc.htm#
    http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/concept_ses_val.htm#HTMDB25030
    I can guarantee that it will be easy

  • Report query XML schema error - Apex Listener 2

    I built a simple query: select * from emp in (Shared components > Report Query)
    When I try to download XML schema for this query (Source Query section) resulting xsd file contains this text: String index out of range: -1
    Shared Apex hosting: 4.2.2.0.0.11
    Print server: Apex Listener 2.0.1

    Hey Saymonc, we're you ever able to find the cause of this issue?  I'm having this happen to me as well.  When I begin using the Report Query functionality, the schema downloaded just fine.  I made an update to a query and began receiving this error.  Now I get the error for ALL of my report queries.  I tried removing them and recreating them, and I continue to receive this error in my schema file, no matter how simple the query.  The data will download just fine, and using the Test Report button works as well.
    Thanks,
    Chris

  • 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

  • Naming standards for reports in Business Objects?

    Dear colleagues,
    I am about to start development of universes, queries and reports in Business Object for a client. Does anyone of you have any tips on naming standards for the reports? The source system that the dataware house is based on is a fund system. Often the name can be some letters and some numbers. Is there any logic behind this that I can follow?
    I will sign points!
    Kind regards
    Silje

    Hi Silje,
    Naming convetions should really tie in with your own processes. So it hard to say there is one for all.
    I generally create a report library. This is a simple list in Excel of the reports. It will contain the following
    Report Id: A number that is unique to each report, e.g. 1000
    Report Name: A short descriptive name, Monthly_Returns
    Report Location: The folder path to the report
    Report Description: A full descriptive name
    Report Contact: The person to contact about the report, developer or support person
    Report Owner: Business Owner of the report
    In WebI I would then call the report 1000_Monthly_Returns. I generally use the folder name to point to the area, so in the case of funds this report would be in the Funds folder.
    Hope this helps
    Alan

  • ORA-00604,ORA-00036,ORA-06521 for any query.

    Hello,
    I have
    ORACLE 10g R2
    Windows Server 2003 32bit
    I have done no changes in my database. No new triggers, nothing at all. Up-till last evening it was working fine , then i started to face this error on every query we fired.
    for ex:-
    SQL>Create table sample(a number);
    ORA-00604: error occurred at recursive SQL level 2
    ORA-00036: maximum number of recursive SQL levels(50) exceeded
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2
    ORA-06521: at line 2I searched on internet for the same but many said its about some mutating table error problem but its not. If i am the only user to work on the database with no trigger enabled then also i get the error.
    I get this error on execution of procedures,functions & all the code which needs to get executed in database.
    What should i do ??? any solution will be appreciated , please also let me know what could have been the reason for this so as next time i would be careful.
    Thanks in advance.

    Hello ,
    I did some R&D on my server & found the solution for the same error. It was so simple but because of the error's description i was getting confused.....
    What i did is had a look at the tablespaces & found that some of the most important tablespaces a full. Like system , ERP, USER, ERPINDEX .....
    So just i increased the size of the tablespace & everything is working fine now ....
    Cheers !!!!
    Thanks to all the people who gave their supportive answers ...

  • Please advise, configuration of BI ivews for report query in EP 7

    System Landscape
    ECC6
    NW EP 7  SP12   ( SSO to BI server and ivews for BI report querys configured)
    NW BI 7   SP12
    Hi folks,
    I'm a basis guy and I'm rookie in BW.
    Currently, I'm performing SP 21 upgrade test. (to fix the IE 8 compatibility issue of EP advised by OSS).
    I did the upgrade test successfully for both EP and BI server.
    However, the BI ivews fail to display pages after the NW EP7 upgrade from SP12 -> SP21)
    I didn't make any change on config or setting after upgrade.
    Then I read some notes and thread on SDN, I think the system is using something like BEx and application integrator for the ivew.
    I checked that all the iviews for BW reporting in my EP version is set as " SAP BW NetWeaver" (NW7).
    Finally, i found one solution to get my ivews work again..can display the page, reading content from BI server.my solution is
    in Portal -> Portal Content -> iviews -> choose corresponding ivew--> and remove the value of field "system" and left it blank.
    (The orginal value is set as SIDCLNTXXX , and I think it is matching to the "Alias" found in system objects
    in Portal -> System Config ->  systemlandscapes --> object - SAP_BW)
    So ..i wonder and feel strange why the iviews  dont need the system object value to work??
    Can someone explain it for me? Is it normal?
    One more scenario:
    If I only have the BI Server upgrade to SP21 and keep EP as SP12.
    The iview works with no problem.
    And any good and direct way for me to test the function , BEx? or something? to make sure the EP and BI connection is working properly after upgrade? 
    I tried the connection test for the system object  - SAP_BW (via system configuration -> system object) passed with no error.
    notes i read:
    917950
    1140854
    Thanks a lots~!!
    Gary

    More info: i tested the BI server : SICF - > SAP BW>BEx  --> service test,   can load page with no problem.
    And as i said, if the EP didn't upgrade to SP12 but only BI ...the ivew work..so i think it is not the problem from BI server?
    Below is the error page of the BI ivew   after upgrade of EP SP12 to SP21.
    Service cannot be reached
    What has happened?
    URL http://host:8000/irj/servlet/prt/portal/prtroot/com.sap.ip.bi.web.portal.integration.launcher call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system BI7 with error code 404 and for the reason Not found.
    The selected virtual host was 0 .
    What can I do?
    Please select a valid URL.
    If you do not yet have a user ID, contact your system administrator.
    ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:SAPBITEST_BI7_00-v:0-s:404-r:Notfound
    HTTP 404 - Not found
    Your SAP Internet Communication Framework Team
    Edited by: Gary Au on Jul 22, 2010 8:54 AM
    Edited by: Gary Au on Jul 22, 2010 8:55 AM

  • Ora-06502 pl/sql numeric or value error in Report Query in oracle apex

    Hello all,
    I need your help...
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    I am using bi publisher to generate PDF reports in oracle apex.
    We were using APEX 4.0 and migrated to 4.2 just a week ago.
    Now we have apex 4.2.
    When I try to Create report query,
    Shared Components >> Report Queries then create.
    and test a report in a create wizard I am getting a error "ORA-06502: PL/SQL: numeric or value error: character string buffer too small".
    I have also applied a patch "16760897".
    This issue is because of number of columns in a query is more then 26.
    If I run a report with 26 or less number of columns then the is working fine, otherwise getting this error.
    My before migration report queries working perfectly even now, but not new queries.
    This issue is also in apex.oracle.com.
    You can see
    Not working  - http://apex.oracle.com/pls/apex/f?p=619:4
    Working - http://apex.oracle.com/pls/apex/f?p=619:2:
    Please give a solution.
    Thanks you.

    check the DB version compatibility with apex 4 or your DB version to apex 4.0 support for upgrade!
    Oracle Application Express Installation Requirements for 4.0

  • Do we have any option to set time limit for report execution

    Hi Experts,
    Please Could any one clarify is there atime  limit to set  for report execution and if it crosses the limit it wud not display a data,
    Thanks in advance
    Nitya

    Hi,
    Basis should be help you in timeout settings on various cases. Time out setting while execution from portal is there.
    Regards,
    Akshay

  • BI Publisher Report Query Error: "character string buffer too small"

    Using apex.oracle.com, I am trying to make a Report Query (Shared Components > Report Queries) based on many columns (around 60).
    When I enter my SQL in the "Source Query" Text Area and then click Test Report I get the following error:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small In order to try to make the simplest test case possible for this, I then tried entering SQL selecting just from DUAL.
    The following SQL fails with the error mentioned above.
    SELECT
    'wibble' as a
    ,'wibble' as b
    ,'wibble' as c
    ,'wibble' as d
    ,'wibble' as e
    ,'wibble' as f
    ,'wibble' as g
    ,'wibble' as h
    ,'wibble' as i
    ,'wibble' as j
    ,'wibble' as k
    ,'wibble' as l
    ,'wibble' as m
    ,'wibble' as n
    ,'wibble' as o
    ,'wibble' as p
    ,'wibble' as q
    ,'wibble' as r
    ,'wibble' as s
    ,'wibble' as t
    ,'wibble' as u
    ,'wibble' as v
    ,'wibble' as w
    ,'wibble' as x
    ,'wibble' as y
    ,'wibble' as z
    ,'wibble' as ab
    ,'wibble' as ac
    ,'wibble' as ad
    ,'wibble' as ae
    ,'wibble' as af
    ,'wibble' as ag
    ,'wibble' as ah
    ,'wibble' as ai
    ,'wibble' as aj
    ,'wibble' as ak
    ,'wibble' as al
    ,'wibble' as am
    ,'wibble' as an
    ,'wibble' as ao
    ,'wibble' as ap
    ,'wibble' as aq
    ,'wibble' as ar
    ,'wibble' as at
    ,'wibble' as au
    ,'wibble' as av
    FROM dualRemoving the last column from this SQL query (bringing the total number of columns down to 45) as follows and then clicking "Test Report" works successfully.
    SELECT
    'wibble' as a
    ,'wibble' as b
    ,'wibble' as c
    ,'wibble' as d
    ,'wibble' as e
    ,'wibble' as f
    ,'wibble' as g
    ,'wibble' as h
    ,'wibble' as i
    ,'wibble' as j
    ,'wibble' as k
    ,'wibble' as l
    ,'wibble' as m
    ,'wibble' as n
    ,'wibble' as o
    ,'wibble' as p
    ,'wibble' as q
    ,'wibble' as r
    ,'wibble' as s
    ,'wibble' as t
    ,'wibble' as u
    ,'wibble' as v
    ,'wibble' as w
    ,'wibble' as x
    ,'wibble' as y
    ,'wibble' as z
    ,'wibble' as ab
    ,'wibble' as ac
    ,'wibble' as ad
    ,'wibble' as ae
    ,'wibble' as af
    ,'wibble' as ag
    ,'wibble' as ah
    ,'wibble' as ai
    ,'wibble' as aj
    ,'wibble' as ak
    ,'wibble' as al
    ,'wibble' as am
    ,'wibble' as an
    ,'wibble' as ao
    ,'wibble' as ap
    ,'wibble' as aq
    ,'wibble' as ar
    ,'wibble' as at
    ,'wibble' as au
    FROM dualSo the question is: Is there a hard-coded limit of 45 columns for a Source Query? Or is there something else causing this error message?
    (For information in the above example I have "Use Generic Report Layout" selected and the output format set to "PDF")
    Thanks very much in advance for any comments or suggestions,
    Andy

    Thanks for the suggestion Simon.
    I just created a view based on the 46-column SELECT statement from dual above and then set "SELECT * FROM myview" as the Source Query.
    Unfortunately I get exactly the same error.
    Thanks,
    Andy

  • Function Returning SQL in BI Publisher Report Query

    I have a report that is based on a SQL Query (PL/SQL Function body returning SQL query). The code is below. I am now trying to create a PDF version of the report using BI Publisher in APEX. When I try to build the Report Query shared component I get a syntax error when entering this code. Does anyone know if it is possible to create a Report Query from a SQL Query (PL/SQL Function body returning SQL query) and if so, how?
    v_sql varchar2(4000);
    begin
    select apexim.exec_summ_bymonth_sql ('D', :p260_time_frame, 12, nvl(:p260_population_sel, 'All'), nvl(:p260_region_sel, 'All'), nvl(:p260_oper_state_sel, 'All'))
    into v_sql
    from dual;
    return(v_sql);
    end;.

    Thanks for the suggestion Simon.
    I just created a view based on the 46-column SELECT statement from dual above and then set "SELECT * FROM myview" as the Source Query.
    Unfortunately I get exactly the same error.
    Thanks,
    Andy

  • Enhancement Req (v4.0): Report Query- Output Format- Derive from Item

    Brief Introduction
    I have 1 major request I would like to make (and 2 lesser ones). The first, I would like to specify custom available output formats for 'Report Query' objects, as well as Reports Regions, Interactive Reports, etc. I believe that this could easily be an instance setting in the Report Server region of the internal workspace, or per workspace / application. Even if not supported on the system wide level, I would recommend that the "Derived from Item" output format "Return Value" be allowed to be returned unaltered to the Report Server. I know that the type is returned as "_xf", and for my purposes I would REALLY like to be able to get something other than the defaults.
    Use Case
    I am creating a custom JasperReports integration (for which I will be launching a public SaaS beta extremely soon). It uses the standard Apex reporting objects (Queries, Layouts, Print Buttons, etc). JasperReports templates are uploaded as Report Layouts and everything works fine. I am, however, wanting to implement as many output formats as are available to me in Jasper...that means Word 07, Excel 07, ODS, ODT, etc. For the items that take a print server override I can handle this in other ways (even though this appears broken [see below]), but for the standard report queries this isn't available. I would basically like the option to define the set of available output formats for the report server, and what the "_xf" returned for each one is.
    Minor Requests
    - Replace Uploaded Templates: If a template is used often and updated, then it has to be changed everywhere...minor irritation.
    - Customize Report Server URL for the Workspace or Application: For SaaS instances, workspace developers may license or have access to reporting solutions that are not (and should not be) available to all of the Oracle instance's workspaces, or may conflict with a service that is already provided by the instance administrators.
    Broken
    When I use the print server override, with the "Use Headers From" option, it appears that neither my content type, nor my content disposition headers are being sent back to the client. This is the work around solution for the non-standard types issue I am requesting enhancement on, so I would like to know what I can do to get this working immediately.
    Additional Info
    As it stands, if the site is available, feel free to sign up for the beta. The beta keys will be exported soon to the instance and made available. Instructions on setup will also follow:
    https://apex.vendelinc.com/apex/f?p=home

    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

  • ORA-01489 Received Generating SQL for Report Region

    I am new to Apex and I am running into an issue with an report region I am puzzled by. Just a foreword, I'm sure this hack solution will get a good share of facepalms and chuckles from those with far more experience. I welcome suggestions and criticism that are helpful and edifying!
    I am on Apex 4.0.2.00.07 running on 10g, I believe R2.
    A little background, my customer has asked an Excel spreadsheet be converted into a database application. As part of the transition they would like an export from the database that is in the same format as the current spreadsheet. Because the column count in this export is dynmic based on the number of records in a specific table, I decided to create a temporary table for the export. The column names in this temp table are based on a "name" column from the same data table so I end up with columns named 'REC_NAME A', 'REC_NAME B', etc. (e.g. Alpha Record, Papa Record, Echo Record, X-Ray Record). The column count is currently ~350 for the spreadsheet version.
    Because the column count is so large and the column names are dynamic I've run into a host of challenges and errors creating this export. I am a contractor in a corporate environmentm, so making changes to the apex environment or installation is beyond my influence and really beyond what could be justified by this single requirement for this project. I have tried procedures and apex plug-ins for generating the file however the UTL_FILE package is not available to me. I am currently generating the SQL for the query in a function and returning it to the report region in a single column (the user will be doing a text-to-column conversion later). The data is successfully being generated, however, the sql for the headers is where I am stumped.
    At first I thought it was because I returned both queries as one and they were joined with a 'union all'. However, after looking closer, the SQL being returned for the headers is about +10K+ characters long. The SQL being returned for the data is about +14k+. As mentioned above, the data is being generated and exported, however when I generate the SQL for the headers I am receiving a report error with "ORA-01489: result of string concatenation is too long" in the file. I am puzzled why a shorter string is generating this message. I took the function from both pages and ran them in a SQL command prompt and both return their string values without errors.
    I'm hopeful that it's something obvious and noobish that I'm overlooking.
    here is the code:
    data SQL function:
    declare
      l_tbl varchar2(20);
      l_ret varchar2(32767);
      l_c number := 0;
      l_dlim varchar2(3) := '''|''';
    begin
      l_tbl := 'EXPORT_STEP';
      l_ret := 'select ';
      for rec in (select column_name from user_tab_columns where table_name = l_tbl order by column_id)
      loop
        if l_c = 1 then
            l_ret := l_ret || '||' || l_dlim || '|| to_char("'||rec.column_name||'")';
        else
            l_c := 1;
            l_ret := l_ret || ' to_char("' || rec.column_name || '")';
        end if;
      end loop;
        l_ret := l_ret || ' from ' || l_tbl;
      dbms_output.put_line(l_ret);
    end;header sql function:
    declare
      l_tbl varchar2(20);
      l_ret varchar2(32767);
      l_c number := 0;
      l_dlim varchar2(3) := '''|''';
    begin
      l_tbl := 'EXPORT_STEP';
      for rec in (select column_name from user_tab_columns where table_name = l_tbl order by column_id)
      loop
        if l_c = 1 then
            l_ret := l_ret || '||' || l_dlim || '||'''||rec.column_name||'''';
        else
            l_c := 1;
            l_ret := l_ret || '''' || rec.column_name || '''';
        end if;
      end loop;
        l_ret := l_ret || ' from dual';
      dbms_output.put_line(l_ret);
    end;-------
    EDIT: just a comment on the complexity of this export, each record in the back-end table adds 12 columns to my export table. Those 12 columns are coming from 5 different tables and are the product of a set of functions calculating or looking up their values. This is export is really a pivot table based on the records in another table.
    Edited by: nimda xinu on Mar 8, 2013 1:28 PM

    Thank you, Denes, for looking into my issue. I appreciate your time!
    It is unfortunately a business requirement. My customer has required that the data we are migrating to this app from a spreadsheet be exported in the same format, albeit temporarily. I still must meet the requirement. I'm working around the 350 columns by dumping everything into a single column, which is working for the data, however, the headers export is throwing the 01489 error. I did run into the error you posted in your reply. I attempted to work around it with the clob type but eneded up running into my string concatentation error again.
    I'm open to any suggestions at this point given that I have the data. I'm so close because the data is exporting, but because the columns are dynamic, the export does me little good without the headers to go along with it.

  • APEX 4.0 Report Query column limitation, 43 column maximum for the result!

    Hi there,
    I'm trying to generate report from Apex 4.0.1, but I got stucked with column limitation when I'm executing the report query.
    Case:
    Environment: oracle 11g, apex 4.0.1, oracle BI 11, windows xp
    Table: My test table is quite simple, by creating a sample table with 44 columns, the column name is random, i.e. column1..column44, column data type is varchar2 (20)
    report query:my report query is also simple, by "select * from testtable"
    Data: no data in my sample table
    Error: then I'll get the error: "HelpORA-06502: PL/SQL: numeric or value error: character string buffer too small"
    solution: If I shrink the table column from 44 to 43, then the report can be generated to xls, pdf, etc.
    Question: Is there any column limitation for Apex report query? I know there's a 32k row size limitation for varchar, but since there's no single data in my table, it shouldn't be the case.
    Does anybody get this issue before? Thanks for any generous input!! :)
    Horatio

    hi marko,
    Thanks for the reply, but i can't find the 45 column limitation from report query and report printing. any clue for this call?
    Regards
    Horatio

  • Need to Pass Active Directory Attributes into OBIEE for use in Report Query

    Hi,
    We're using OBIEE 11.1.1.5 and have integrated it with AD security. Users successfully log into OBIEE and BIP (which is integrated with OBIEE) using their network/AD accounts.
    Next step for us is to be able to pass some AD attributes that are on the user accounts into OBIEE and BIP so we can restrict data queries for the person logged in.
    I've searched the web and so far have only come up with specific steps for setting this up in BIP. Since BIP is integrated with OBIEE, we have not set any of the MSAD/LDAP security up there - it is all in OBIEE. I have been unable to find the equivalent for adding the attribute names for data query bind variables.
    With our current setup, we are unable to filter the report data automatically based on who has logged into the application (analytics and BIP). We have security setup within the catalog so only certain AD groups can access objects, but beyond that we need to be able to secure the data using AD attribute information. For example, all of our users should be able to access an Open Purchase Order report, but they should only be able to see their own purchase orders - not everyone in the company.
    Anyway, we're looking to be able to pass AD attributes into OBIEE so that we can use this data in our Analytics and BIP queries.
    How can we get this setup?
    Thank you in advance!
    Suzanne

    A fairly common problem, see:
    http://www.williamrobertson.net/documents/comma-separated.html
    http://www.oracle-base.com/articles/misc/DynamicInLists.php
    http://tkyte.blogspot.com/2006/06/varying-in-lists.html

Maybe you are looking for