ORA-06502 in the Tree Report

I am encountering the following error on my Tree report occasionally. "Unexpected error ORA-06502: PL/SQL: numeric or value error: character string buffer too small". Apex version 3.x (I think not sure), Database 10.1.0.4
I have noticed that I can keep on expanding nodes a couple of times and then suddenly I get error. After I logoff and logon again, I can get tree displayed and then after few expands I receive the error. I have reduced MAX LEVEL from 5 to 1. Here is the query and the table:
select "METHOD_ID" id,
"P_METHOD_ID" pid,
method_id || ' : ' || P_method_id || ' : ' ||
PROJECT_NAME || ' : ' ||
package_name || ' : ' ||
class_name || ' : ' ||
method_name name,
'f?p=&APP_ID.:10:&SESSION.::NO::GLB_METHOD_ID:'||"METHOD_ID" link,
null a1,
null a2
from java2java_usedby h .
The table java2java is:
CREATE TABLE JAVA2JAVA_USEDBY
METHOD_ID NUMBER(15) NOT NULL,
PROJECT_NAME VARCHAR2(200 BYTE),
COMPONENT_NAME VARCHAR2(200 BYTE),
PACKAGE_NAME VARCHAR2(200 BYTE),
CLASS_NAME VARCHAR2(200 BYTE),
METHOD_NAME VARCHAR2(200 BYTE),
P_METHOD_ID NUMBER
NOLOGGING ;
CREATE UNIQUE INDEX JAVA2JAVA_USEDBY_U1 ON JAVA2JAVA_USEDBY
(P_METHOD_ID, METHOD_ID)
NOLOGGING;
This table allows a row to have multiple parents. So for a given method_id, there could be more than one p_method_id.
Method ID values are 10-12 digits

Vasant - It would be ideal if you could show this problem on apex.oracle.com.
There was an error with similar symptoms reported and discussed here: Tree error, after Expand All, then collapsing any node, ORA-6502/6512 , so if you could determine the version of Application Express you are using that might be useful.
Scott

Similar Messages

  • Got error ORA-06502 when creating a report page

    Hi,
    I got ORA-06502 error message when trying to create a report page using one particular query (see below). It happened in the 'SQL Query' step. After put query in the text box and click on 'Next' button, the error message read
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    Exactly same query running in sqlplus session against same database and same schema can run thru fine.
    I wonder if anybody can give me a pointer what could be wrong with the query, and how to debug.
    The query is
    WITH o AS
    SELECT a.manager, m.owner
    FROM man_hierarchy_v m,
         SELECT owner manager
         FROM man_hierarchy_v
         WHERE manager_ladder LIKE '%-CROZWAT-%'
         AND olevel =
              (SELECT olevel + 1 FROM man_hierarchy_v WHERE owner = 'CROZWAT')
         ORDER BY owner
    ) a
    WHERE manager_ladder LIKE '%-' || a.manager || '-%'
    SELECT manager,
         code, TO_CHAR(code/total*100, '999.9') code_perc,
         code_symptoms, TO_CHAR(code_symptoms/num_symptoms*100, '999.9') code_sym_perc,
         env, TO_CHAR(env/total*100, '999.9') env_perc,
         env_symptoms, TO_CHAR(env_symptoms/num_symptoms*100, '999.9') env_sym_perc,
         test, TO_CHAR(test/total*100, '999.9') test_perc,
         test_symptoms, TO_CHAR(test_symptoms/num_symptoms*100, '999.9') test_sym_perc,
         tbd, TO_CHAR(tbd/total*100, '999.9') tbd_perc,
         tbd_symptoms, TO_CHAR(tbd_symptoms/num_symptoms*100, '999.9') tbd_sym_perc,
         cnd, TO_CHAR(cnd/total*100, '999.9') cnd_perc,
         cnd_symptoms, TO_CHAR(cnd_symptoms/num_symptoms*100, '999.9') cnd_sym_perc,
         latent, TO_CHAR(latent/total*100, '999.9') latent_perc,
         latent_symptoms, TO_CHAR(latent_symptoms/num_symptoms*100, '999.9') latent_sym_perc,
         behavior, TO_CHAR(behavior/total*100, '999.9') behavior_perc,
         behavior_symptoms, TO_CHAR(behavior_symptoms/num_symptoms*100, '999.9') behavior_sym_perc,
         dep_labels, TO_CHAR(dep_labels/total*100, '999.9') dep_labels_perc,
         dep_labels_symptoms, TO_CHAR(dep_labels_symptoms/num_symptoms*100, '999.9') dep_labels_sym_perc,
         total, num_symptoms
    FROM
    SELECT manager, SUM(code) code, SUM(code_symptoms) code_symptoms,
         SUM(cnd) cnd, SUM(cnd_symptoms) cnd_symptoms,
         SUM(env) env, SUM(env_symptoms) env_symptoms,
         SUM(behavior) behavior, SUM(behavior_symptoms) behavior_symptoms,
         SUM(latent) latent, SUM(latent_symptoms) latent_symptoms,
         SUM(dep_labels) dep_labels, SUM(dep_labels_symptoms) dep_labels_symptoms,
         SUM(test) test, SUM(test_symptoms) test_symptoms,
         SUM(tbd) tbd, SUM(tbd_symptoms) tbd_symptoms,
         COUNT(probid) total,
         SUM(num_symptoms) num_symptoms
    FROM
    SELECT o.manager, p.probid, NVL(num_symptoms, 0) num_symptoms,
         DECODE(type, 'C', 1, 0) code,
         CASE WHEN type = 'C' THEN num_symptoms ELSE 0 END code_symptoms,
         DECODE(type, 'CND', 1, 0) cnd,
         CASE WHEN type = 'CND' THEN num_symptoms ELSE 0 END cnd_symptoms,
         DECODE(type, 'E', 1, 0) env,
         CASE WHEN type = 'E' THEN num_symptoms ELSE 0 END env_symptoms,
         DECODE(type, 'L', 1, 0) behavior,
         CASE WHEN type = 'L' THEN num_symptoms ELSE 0 END behavior_symptoms,
         DECODE(type, 'LATENT', 1, 0) latent,
         CASE WHEN type = 'LATENT' THEN num_symptoms ELSE 0 END latent_symptoms,
         DECODE(type, 'O', 1, 0) dep_labels,
         CASE WHEN type = 'O' THEN num_symptoms ELSE 0 END dep_labels_symptoms,
         DECODE(type, 'T', 1, 0) test,
         CASE WHEN type = 'T' THEN num_symptoms ELSE 0 END test_symptoms,
         DECODE(type, 'TBD', 1, 0) tbd,
         CASE WHEN type = 'TBD' THEN num_symptoms ELSE 0 END tbd_symptoms
    FROM lrg_problem_v3 p, o
    WHERE p.assigned = o.owner
    AND p.cdate BETWEEN '16-DEC-08' AND '15-JAN-09'
    AND last_label LIKE 'RDBMS_MAIN_LINUX' || '_%'
    AND lrg LIKE 'lrg' || '%'
    GROUP BY manager
    ORDER BY manager
    I tried to remove all the TO_CHAR functions but same error message was returned.
    Thanks,
    Mingying

    This version of Apex comes with database release 11.1.0.6.0
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    PL/SQL Release 11.1.0.6.0 - Production
    CORE 11.1.0.6.0 Production
    TNS for Linux: Version 11.1.0.6.0 - Production
    NLSRTL Version 11.1.0.6.0 - Production
    Following information might also be helpful.
    Product Build: 3.1.0.00.32
    Schema Compatibility: 2007.09.06
    NLS_CHARACTERSET: AL32UTF8
    DAD CHARACTERSET: UTF-8
    JOB_QUEUE_PROCESSES: 1000
    Thanks,
    Mingying

  • ORA-06502 on  'SQL query' report with sort in 'Report Attributes'

    Hi All,
    We get the next error if we set sorting on a column in a 'Report' based on a 'SQL query'. Removing the sort, error disappeares:
    failed to parse SQL query:
    ORA-06502: PL/SQL: numeric or value error: NULL index table key value
    Any suggestions?
    Erik

    Erik,
    Thanks, this explains it. By specifying the request as part of your URL you run into the recently uncovered issue. The request you're setting is REMFROMLIST and ADD2LIST. You probably either have links that include those requests or you have branches where you specify them. Either way, in order to get reports sorting to work, you'll have to make sure that the request strings are not part of your URL. This is a work-around and the upcoming HTML DB patch release will solve this issue.
    One way of avoiding this is to have computations on the previous pages that set a napplication level or page level item to the REMFROMLIST and ADD2LIST values and then you can use those items for your conditions that are currently evaluating those strings.
    Hope this helps and sorry for the inconvenience,
    Marc

  • Ora-06502 using the PKG_LOOK_AND_FEEL.Paint_Block on Linux

    Hi All.
    I have ported an application from development (win - client machine) to the application server on Linux.
    An error (ora-06502) is shown where calling the PKG_LOOK_AND_FEEL.Paint_Block.
    I have verified all parameters have a value when this procedure is called ... Any ideas of what may be causing this one ...?
    Best regards, Luis ....!

    Hello,
    Please, don't ask questions on the LAF project on this forum. Send your questions to the dedicated email : [email protected]
    Thank you,
    Francois

  • Ideas for working around ORA-06502: character string buffer too small on Interactive report

    Hello,
    This is for Apex 4.2.  We are trying to create an interactive report.  The report is for something similar to a time tracking application.  We are trying to concat a comments column while summing the hours.  For example,
    select TASK_NAME, sum(HOURS), to_char(XMLAGG(XMLELEMENT(E,E.COMMENTS || ' : ')).EXTRACT('//text()').getstringval()) USER_COMMENTS from ......
    This query works fine if we are looking only at a 1 week window.  The issue we are experiencing is that when we expand the range of the query to include data from 3 months, we hit ORA-06502 in the interactive report.  If we remove this column from the Interactive report, then the report runs fine.
    Does anyone have any ideas on how we might be able to work around this?  I am guessing we are hitting the 32k limit on the report.  Ideally we would just show the last X number of comments and then have a link to view all the comments
    Any help would be appreciated
    Thanks
    Mike

    ListAGG throws an ORA-01489 for varchar2 > 4000 bytes
    OP has an ORA-06502 --> the IR is running into a 4k/32k limit.
    quick solution: wrap USER_COMMENTS ListAGG in a substr( ...., 1, 4000)
    Longer solution, use a subquery to modify the comments based on ROW_NUMBER() (ie after nth row, change it to NULL)
    with
    -- simulating data
    t as (select task_id, sysdate - lv as date_entered
      ,round(dbms_random.value(1,24)) hours
      , '-*' || lv || '.' || task_id || '*-' as user_comments
    from ( select level as task_id from dual connect by level <=10 ), (select level lv from dual connect by level < 1000)
    -- modify data
    modified_data as (
      select task_id, hours, date_entered
        ,case
          when row_number() over (partition by task_id order by date_entered desc) < 5
            then user_comments
          else null
         end USER_COMMENTS
        from t)
    select task_id, sum(hours) total_hours,
      listagg( user_comments  ) within group (order by date_entered desc)
      || case when count(*) >= 5 then '! MORE COMMENTS !' else null end
        as user_comments
    from modified_data
    group by task_id;

  • Drill down in tree report

    Hi gurus,
    This is regarding the drill down in the Tree report.
    My scenario is,
    i am doing a budget variance report which displays the report in tree format.
    i have texts for different nodes in the tree, along with that i have a 10 feilds which i display using fieldcat in output along with nodes.
    now i want to have the drill down to the 2 of the fields, where it has to go to some transaction.
    i tried with hotspot in fieldcat definition but it is not working.
    please can u tell me a solution as how can i do this drill down.
    thanks in advance.
    u will be rewarded heavily.

    Hi Vipin,
    You can try with following example:
    *& Report  ZPRG                                                *
    &--INTERACTIVE ALV REPORT PROGRAM--
    &This program displays order detais for a particular customer----
    REPORT  zprg                              .
    --TYPE POOLS--
    TYPE-POOLS slis.
    --TABLES--
    TABLES : kna1, vbak.
    --DATA TYPES--
    TYPES : BEGIN OF ty_vbak,
    vbeln TYPE vbak-vbeln,
    erdat TYPE vbak-erdat,
    netwr TYPE vbak-netwr,
    END OF ty_vbak.
    TYPES : BEGIN OF ty_vbap,
    posnr TYPE vbap-posnr,
    arktx TYPE vbap-arktx,
    werks TYPE vbap-werks,
    END OF ty_vbap.
    --WORK AREAS--
                              FOR FIRST PAGE                            *
    DATA w_fcat TYPE slis_fieldcat_alv.   "Used as Header for Field Catalog
    DATA w_vbak TYPE ty_vbak.             "Used as Header for Data Table
    DATA w_events TYPE slis_alv_event.    "Used as header for Events Table
    DATA w_comments TYPE slis_listheader. "Used as Header for Comments Table
                               SECOND PAGE                              *
    DATA w2_fcat TYPE slis_fieldcat_alv.   "Used as Header for Field Catalog
    DATA w2_vbap TYPE ty_vbap.             "Used as Header for Data Table
    DATA w2_events TYPE slis_alv_event.    "Used as header for Events Table
    DATA w2_comments TYPE slis_listheader."Used as Header for Comments Table
    --INTERNAL TABLES--
                              FOR FIRST PAGE                            *
    DATA t_fcat TYPE slis_t_fieldcat_alv.   "Table for Field Catalog
    DATA t_vbak TYPE ty_vbak OCCURS 1.      "Data Table
    DATA t_events TYPE slis_t_event.        "Table for events
    DATA t_comments TYPE slis_t_listheader. "Comments table
                               SECOND PAGE                              *
    DATA t2_fcat TYPE slis_t_fieldcat_alv.   "Table for Field Catalog
    DATA t2_vbap TYPE ty_vbap OCCURS 1.      "Data Table
    DATA t2_events TYPE slis_t_event.        "Table for events
    DATA t2_comments TYPE slis_t_listheader. "Comments table
    *****************VIPIN: START*****************************
    DATA: V_REPID LIKE SY-REPID.
    V_REPID = SY-REPID.
    *****************VIPIN: END*******************************
    --SELECTION SCREEN--
    PARAMETERS p_custno TYPE kna1-kunnr.
    --FILLING FIELD CATALOG--
                              FOR FIRST PAGE                            *
    w_fcat-col_pos = 1.
    w_fcat-fieldname = 'VBELN'.
    w_fcat-seltext_m = 'ORDER NUMBER'.
    APPEND w_fcat TO t_fcat.
    w_fcat-col_pos = 2.
    w_fcat-fieldname = 'ERDAT'.
    w_fcat-seltext_m = 'ORDER DATE'.
    APPEND w_fcat TO t_fcat.
    w_fcat-col_pos = 3.
    w_fcat-fieldname = 'NETWR'.
    w_fcat-seltext_m = 'ORDER VALUE'.
    APPEND w_fcat TO t_fcat.
                               SECOND PAGE                              *
    w2_fcat-col_pos = 1.
    w2_fcat-fieldname = 'POSNR'.
    w2_fcat-seltext_m = 'ITEM NUMBER'.
    APPEND w2_fcat TO t2_fcat.
    w2_fcat-col_pos = 2.
    w2_fcat-fieldname = 'ARKTX'.
    w2_fcat-seltext_m = 'ITEM DESCRIPTION'.
    APPEND w2_fcat TO t2_fcat.
    w2_fcat-col_pos = 3.
    w2_fcat-fieldname = 'WERKS'.
    w2_fcat-seltext_m = 'PLANT'.
    APPEND w2_fcat TO t2_fcat.
    --FILLING DATA TABLE--
                              FOR FIRST PAGE                            *
    SELECT vbeln
           erdat
           netwr
    FROM vbak
    INTO TABLE t_vbak
    WHERE kunnr = p_custno.
    SORT t_vbak BY vbeln.
                               SECOND PAGE                              *
    DATA FOR 2ND PAGE IS FILLED IN THE SUBROUTINE HANDLING USER_COMMAND *
    --FILLING EVENTS TABLE--
    w_events-name = 'TOP_OF_PAGE'.
    w_events-form = 'SUB1'.
    APPEND w_events TO t_events.
    w_events-name = 'USER_COMMAND'.
    w_events-form = 'SUB2'.
    APPEND w_events TO t_events.
    --FILLING COMMENTS TABLE--
    w_comments-typ = 'H'.
    w_comments-info = 'CUSTOMER ORDER INFORMATION'.
    APPEND w_comments TO t_comments.
    w_comments-typ = 'S'.
    w_comments-key = 'Sold To Party'.
    w_comments-info = p_custno.
    APPEND w_comments TO t_comments.
    -----PASSING FIELD CATALOG AND THE DATA TABLE TO THE FUNCTION-----
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
        I_INTERFACE_CHECK                 = ' '
        I_BYPASSING_BUFFER                = ' '
        I_BUFFER_ACTIVE                   = ' '
          i_callback_program                = V_REPID
        I_CALLBACK_PF_STATUS_SET          = ' '
        I_CALLBACK_USER_COMMAND           = ' '
        I_CALLBACK_TOP_OF_PAGE            = ' '
        I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
        I_CALLBACK_HTML_END_OF_LIST       = ' '
        I_STRUCTURE_NAME                  =
        I_BACKGROUND_ID                   = ' '
        I_GRID_TITLE                      =
        I_GRID_SETTINGS                   =
        IS_LAYOUT                         =
          it_fieldcat                       = t_fcat
        IT_EXCLUDING                      =
        IT_SPECIAL_GROUPS                 =
        IT_SORT                           =
        IT_FILTER                         =
        IS_SEL_HIDE                       =
        I_DEFAULT                         = 'X'
        I_SAVE                            = ' '
        IS_VARIANT                        =
          it_events                         = t_events
        IT_EVENT_EXIT                     =
        IS_PRINT                          =
        IS_REPREP_ID                      =
        I_SCREEN_START_COLUMN             = 0
        I_SCREEN_START_LINE               = 0
        I_SCREEN_END_COLUMN               = 0
        I_SCREEN_END_LINE                 = 0
        IT_ALV_GRAPHICS                   =
        IT_HYPERLINK                      =
        IT_ADD_FIELDCAT                   =
        IT_EXCEPT_QINFO                   =
        I_HTML_HEIGHT_TOP                 =
        I_HTML_HEIGHT_END                 =
      IMPORTING
        E_EXIT_CAUSED_BY_CALLER           =
        ES_EXIT_CAUSED_BY_USER            =
      TABLES
        t_outtab                          = t_vbak
      EXCEPTIONS
        PROGRAM_ERROR                     = 1
        OTHERS                            = 2
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
                Subroutine for the Event TOP_OF_PAGE
    FORM sub1 .
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          it_list_commentary       = t_comments
          i_logo                   = 'COMPANY LOGO'
      I_END_OF_LIST_GRID       =
    ENDFORM.                                                    " sub1
                Subroutine for the Event USER_COMMAND
    Here u_comm contains the function code of the selected function
    and slis_field is a structure containing cursor information
    FORM sub2 USING u_comm LIKE sy-ucomm rs_field TYPE slis_selfield.
    CASE u_comm.
        WHEN '&IC1'.
          IF rs_field-fieldname = 'VBELN'.
            SELECT posnr
                   arktx
                   werks
            FROM vbap INTO TABLE t2_vbap WHERE vbeln = rs_field-value.
          ENDIF.
      ENDCASE.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
        I_INTERFACE_CHECK                 = ' '
        I_BYPASSING_BUFFER                = ' '
        I_BUFFER_ACTIVE                   = ' '
        I_CALLBACK_PROGRAM                = ' '
        I_CALLBACK_PF_STATUS_SET          = ' '
        I_CALLBACK_USER_COMMAND           = ' '
        I_CALLBACK_TOP_OF_PAGE            = ' '
        I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
        I_CALLBACK_HTML_END_OF_LIST       = ' '
        I_STRUCTURE_NAME                  =
        I_BACKGROUND_ID                   = ' '
        I_GRID_TITLE                      =
        I_GRID_SETTINGS                   =
        IS_LAYOUT                         =
          it_fieldcat                       = t2_fcat
        IT_EXCLUDING                      =
        IT_SPECIAL_GROUPS                 =
        IT_SORT                           =
        IT_FILTER                         =
        IS_SEL_HIDE                       =
        I_DEFAULT                         = 'X'
        I_SAVE                            = ' '
        IS_VARIANT                        =
        IT_EVENTS                         =
        IT_EVENT_EXIT                     =
        IS_PRINT                          =
        IS_REPREP_ID                      =
        I_SCREEN_START_COLUMN             = 0
        I_SCREEN_START_LINE               = 0
        I_SCREEN_END_COLUMN               = 0
        I_SCREEN_END_LINE                 = 0
        IT_ALV_GRAPHICS                   =
        IT_HYPERLINK                      =
        IT_ADD_FIELDCAT                   =
        IT_EXCEPT_QINFO                   =
        I_HTML_HEIGHT_TOP                 =
        I_HTML_HEIGHT_END                 =
      IMPORTING
        E_EXIT_CAUSED_BY_CALLER           =
        ES_EXIT_CAUSED_BY_USER            =
        TABLES
          t_outtab                          = t2_vbap.
      EXCEPTIONS
        PROGRAM_ERROR                     = 1
        OTHERS                            = 2
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                                                    "sub2

  • Webutil ORA-06502

    Hello,
    When using webutil.file_selection_dialog we are getting an ORA-06502 when the directory structure and filename is 255 char long. Is this a known limitation?
    When enabling webutil logging we get the following output:
    2003-aug-22 13:44:53.640 WUF[getProperty()] Value of WUF_GFN_OPENFILE=S:\Exchange\TestData\Product.development[1]proposal\Project..201.Portal\Case Data\Hull\TestData\Product.development[1]proposal\Project..201.Portal\Case Data\Hull\TestData\Product development proposal\Project Portal\Case Data\Extra[234].long path\short.txt
    sun.plugin.cache.DownloadException
    /Vidar

    I tried a simple case and it worked for 279 characters.
    e.g. myString VARCHAR2(400);
    BEGIN
    Webutil_File.File_Selection_Dialog();
    message (myString);
    END;
    works ok.
    My guess is maybe you are assigning it to a field which is not big enough.
    Regards
    Grant Ronald
    Forms Product Management

  • Attached library & ora-06502

    Running forms 5.0.6.8.0 and
    Oracle 8.0.5.0.0
    I am using an attached library . Package1 consists only of a package spec that defines a set of variables. Packages 2 thru 5 consist of various functions and procedures some of which reference the variables defined in Package 1.
    My problem is this.
    If I execute package2.functionA in form1 in the pre-form trigger, it executes perfectly. If I execute package2.functionA in form2 in the pre-form trigger it fails and raises the error ORA-06502. The code in both pre-form triggers are identical. I can see no obvious differences between the forms.
    If I rewrite package2 and replace the package1 variable with a local variable defined in package2, the function runs fine in both form1 and form2. I am totally confused.
    Any suggestions.

    i minimised it in the forum to just let u know the gist without going into the gritty details =)
    oh i realised my problem ...heheh its a stp error
    so sorry =)

  • ORA-06502: PL/SQL: at the end of an Excel Download report

    Hi,
    Within my apex application I have the possibility to download a file from ie. page 7 (which is linked to a query in page 8). When I open the downloaded file, I find an error at the end of the sheet:
    <pre>report error:
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error</pre>
    The thing is, the query that retrieves this report works perfectly, and when put in sql developer, it retrieves the same number of rows.
    So it must be that after the query has finished with all the rows, in encounters some kind of character ie. a space , that can´t convert to number and thus gives the error.
    Something worth noting is that, when I actually execute the page directly (page 8), that executes de query, it doesn´t give me the error on the excel.
    Any recommendations on a possible reason are welcome.
    Thank you,
    Javier

    I am also hitting this problem. Any pointer plz..

  • Report error while download the report.-ORA-06502

    *"report error:ORA-06502: PL/SQL: numeric or value error: character string buffer too small."*
    When I trying to download the classical report,It give the above error when report having the more than 26 column to print,
    The download report format what ever may be except .csv.
    Any solution for this?
    Edited by: 945115 on Aug 29, 2012 12:35 AM
    Edited by: 945115 on Aug 29, 2012 12:35 AM

    Pratap.,
    Error in classical report download by print server link.This is a PDF output that your are generating?
    Which Report Server have you configured? This error is coming from Report Server.
    The Standard Report Server has its limitations. If are using Std then maybe you have hit one of them.
    Cheers,
    PS: Change you handle to something better than 945115

  • Report error:ORA-06502:character string buffer too small. urgent!!

    Hi guys,
    My APEX version is 3.0.1.00.08, my application run on my test environment, but on PROD environment, it raised the error:
    report error:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    In this page, on the left is a tree, the right side is a tabular form, when I click one tree node, it will pass the current node id to the form and the form will display the children data. When I click some tree node, it will raise the ORA-06502 error, but when click some other nodes, it is correct. I don't know why. And on my test environment, it has no this error, the test environment has same version with prod environment, only has less data in database. Could you help me???
    I searched in forum, someone says it's LOV problem, if it's LOV problem, all the nodes should have error, why click some nodes are ok?
    Thanks !
    Jessica

    I don't think it is related only to the number of rows but also to the content of the rows. So, counting only the number of rows doesn't say anything about if it is going to work or not. My question: can't you filter those entries? Making a choice between 250 entries in a tabular form isn't a simple task. Using popup-key LOV instead would also be a solution. However, if you use popup-key LOV be aware of the fact that you need two index numbers for those.
    Denes Kubicek
    http://deneskubicek.blogspot.com/
    http://www.opal-consulting.de/training
    http://apex.oracle.com/pls/otn/f?p=31517:1
    -------------------------------------------------------------------

  • Version 3.1 fault - ORA-06502 error when creating SQL Report Region/Page

    I usually perfect my query in SQL*PLUS before I create a new report region.
    Consequently, I copy the code into the region wizard to create the new page. However, since we have upgraded to Version 3.1, virtually every report I have tried to create has created the following error:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    It would appear that a maximum of 960 characters can be used to create the region/page. Perversely, once the page/region has been created, I can then edit the source and include as much code as I want (so far I've not run up against a limit)
    As it's just annoying, but not stopping me doing what I wanted to do, I've not got around to mentioning this error previously, but it occurred to me that I should (so I am!)
    David

    Hi David,
    Thank you for reporting this. Unfortunately, this was a regression introduced in Application Express 3.1. The workaround is to edit the region, as you suggested. This has been filed as Bug 6956070 and will be corrected in the forthcoming Application Express 3.1.1 patch set.
    Joel

  • Sql Query (updateable Report) returning ORA-06502: PL/SQL: numeric or value

    Hi I have a Sql Query Report Region as defined below. On the report attributes I am not using any "Row Selector". In a After submit process I try to print out the results of the value I have entered in as a value in updatable report and i get the error: I am doing this as a test before i use the data to insert into another table...
    I receive this error if I enter in a characters (not numeric) into the "Field Value" field.:
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error.
    If I enter in a numeric into the "Field Value" text box, then I get the value displayed back without error. I need to be able to enter a varchar value without error.
    My SQL QUERY is:
    select i.INDEXED_FIELD_ID, i.field_name,
    HTMLDB_ITEM.TEXT(3,d.indexed_field_value) field_value,
    decode(f.required, 0, 'O', 1, 'R', 'NOT USED') REQUIRED
    from XXVG_EFILE_DOCUMENT_FIELDS D,
    xxvg_efile_type_fields f, xxvg_efile_indexed_fields i
    WHERE f.indexed_field_id = i.indexed_field_id
    and f.required in (0,1)
    and i.indexed_field_id = d.indexed_field_id(+)
    and d.document_id(+) = -1
    and f.document_type_id = :p21_doc_type
    My after submit process is the following...**Note** I am using P21_test as a field just to display my test. I receive the value back just fine without error if numeric. If varchar, that is when the problems occur. I have used just a length variable like the lettter 't' for testing and still receive the error.
    DECLARE
    vRow BINARY_INTEGER;
    BEGIN
    -- update field values
    FOR i IN 1 .. HTMLDB_APPLICATION.g_f03.COUNT -- your field value
    LOOP
    vRow := HTMLDB_APPLICATION.g_f03(i);
    IF vRow is Not NULL --means the field has data in it.
    THEN
    :p21_test := HTMLDB_APPLICATION.G_F03(i); --set a variable to the field with data.
    END IF;
    END LOOP;
    END;
    Is there a conversion I need to do? I do not want to do this via checkboxes as I dont want the user have to check a checkbox and then enter a value in. I just want a blank text box the user can enter a value in and then i can do an insert.
    Thanks So much.

    Thanks Scott, That did do the trick as the varchar is now displayed of the entered item.
    How do i also display the value of indexed_field_id as well.
    I have an insert where i need the indexed field id and the entered field value.
    Thanks in advance.

  • Report error: ORA-06502: PL/SQL: numeric or value error: character string b

    I have a form which uses a customer form/report, drop downs etc..
    the debug shows it running this statement
    ...Execute Statement: begin begin SELECT distinct initcap(RTRIM (LTRIM (e.surname, ' *0123456789-/:.?,'), ' *0123456789-/:.?,') || ', ' || RTRIM (LTRIM (e.first_name, ' *0123456789-/:.?,'), ' *0123456789-/:.?,' )) empname, e.ID bulk collect into wwv_flow_utilities.g_display,wwv_flow_utilities.g_value FROM dms.dms_employees@dmsprd e, dms.dms_employee_contracts@dmsprd ec WHERE e.ID = ec.emp_id and e.surname like '%%' AND :p75_date BETWEEN ec.start_date AND NVL (ec.end_date, :p75_date) AND e.brh_id = 3654 ORDER BY 1; end; end;
    Then says
    "report error: ORA-06502: PL/SQL: numeric or value error: character string buffer too small"
    Any Ideas?
    Thanks
    Dean

    Denes Kubicek wrote:
    A select list is limited in size. I am not sure what the limit is but that is definitelly the case.The maximum size for the HTML generated for a select list is 32K.
    86 options sounds on the low side to be hitting that limit, but there are other concerns to this as well. Scrolling through hundreds/thousands of options in a select list is a pain for users, and huge select lists produce bloated pages that impact load times and network bandwidth. That list of around 200 countries you find on many sites is about the sensible maximum length for a select list.
    You should use popups.Indeed.

  • Report error:ORA-06502: PL/SQL: numeric or value error: character to number

    The oracle application express environment is created by installing the HTTP Server on the windows server and the application express 3.2.1 components on the 11.1.0.7 oracle database on UNIX. The installation is successfully and have not seen any issues during the installation. After completing all the steps, when tried to login and click the application builder or workspace components, I see the error message
    report error:ORA-06502: PL/SQL: numeric or value error: character to number.
    This error message is seen on most of the pages when trying to accessed and not able to understand the reasons behind it. Its a brand new environment setup and not even presented to developers to test it.
    Below error message is always seen when trying to access most of the components like application builder, schema comparison and some other tabs. Please advice
    report error:
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    Edited by: user589320 on Jun 9, 2011 5:17 PM

    I think its better you use APEX 4.x version ratherthan using old version.
    You will get more features and some bug fixes and also it's easy for you to get some help when you need.
    * If this answer is helpfull or correct then please mark it and grant the points.

Maybe you are looking for