5 Replies Latest reply on Nov 19, 2018 6:39 PM by fme

    Apex 18.2 Reports 32k issue. Is that a bug?

    fme

      >>>     I tried to retrieve and display a report column with 32k characters like

      select '<4001 chars>' data from dual;

      or

      select data from data;  #with more than 4000 chars per row

      I Always got ora-06502, not only in CR but also in IR.

       

      >>>> Retrieving less than 3900 chars is no Problem like:

      select data from data where length(data) < 3900;  #having multi-Byte chars in mind.

       

      Obviously there is still a 4k Limit !!

      >>>> In Apex 5.1.4 it works !!

      The DB is 12c.

       

      >>>>  Any hint, how to solve  ora-6502 with 32k data?

        • 1. Re: Apex 18.2 Reports 32k issue Is that a Buck?
          fac586

          user590088 wrote:

           

          Apex 18.2 Reports 32k issue Is that a Buck?

          I am unable to extract any meaning from the thread's subject line. Please explain/rephrase using standard APEX/Oracle/web terminology.

          I tried to retrieve and display a report column with 32k characters like

           

          select '<4001 chars>' data from dual;

          or

          select data from data; #with more than 4000 chars per row

          I Always got ora-06502, not only in CR but also in IR.

          There is a 32KB limit on the size of report rows. This includes user data and all HTML mark-up generated by the APEX engine and/or report template.

          • 2. Re: Apex 18.2 Reports 32k issue Is that a Buck?
            Alli Pierre Yotti

            Which Database Version please? I think the IR and CR ROW LENGTH LIMIT is 32K

            Take also a look here

            Apex 18.1 Interactive report column Varchar2 limit.

            • 3. Re: Apex 18.2 Reports 32k issue. Is that a bug?
              Carsten Czarski-Oracle

              Hi,

               

              does it work when you convert the column explicitly to a CLOB in your query ...?

               

              select to_clob( {column or expression with more than 4k} ) as column_name, {other columns} from table

               

              Best regards

               

              -Carsten

              • 4. Re: Apex 18.2 Reports 32k issue. Is that a bug?
                fac586

                user590088 wrote:

                Update your forum profile with a recognisable username instead of "user590088".

                >>> I tried to retrieve and display a report column with 32k characters like

                select '<4001 chars>' data from dual;

                or

                select data from data; #with more than 4000 chars per row

                I Always got ora-06502, not only in CR but also in IR.

                 

                >>>> Retrieving less than 3900 chars is no Problem like:

                select data from data where length(data) < 3900; #having multi-Byte chars in mind.

                 

                Obviously there is still a 4k Limit !!

                >>>> In Apex 5.1.4 it works !!

                The DB is 12c.

                 

                >>>> Any hint, how to solve ora-6502 with 32k data?

                Stop changing the original post. If you want to add further information or respond to another post, use the Reply buttons.

                 

                See the User Guide for help on using this site.

                • 5. Re: Apex 18.2 Reports 32k issue. Is that a bug?
                  fme

                  I have a complex 5.1.4 application, that works and that I want to upgrade to 18.2.The import to the upgraded 18.2 raises ora-06502

                  but works in SQL-Workshop.

                   

                  >>>> My simple example SQLs from above do not work either! You may try it for your own.

                   

                  Therefore I think it is a bug during Import and installation, because types and collections in 18.2 are correctly defined with varchar2(32767).

                   

                  The clob conversion would not fit my application.