Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.3K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
APEX 4.2 Report Exports and Column Limitations

I have an APEX 4.2 application where we want to give users the ability to download a very large report into Excel. The report has 325 columns and over 20k rows. I've tried both Interactive and Classic with the following results:
When creating a Classic Report with all of the columns, an error is generated = ORA-01461: can bind a LONG value only for insert into a LONG column.
When creating an Interactive Report with all of the columns, an error is generated = ORA-06502: PL/SQL: numeric or value error: character string buffer too small.
I do not need to display the report on the page, but require only a way to download the results of the report's query to an Excel file, much like the reports' built-in Download feature. I would prefer, in fact, to not display the oversized query results.
Best Answer
-
Could you just use some PL/SQL to generate a text file that happens to be comma delimited?
Answers
-
Is the query from a single table or multiple tables? There are multiple routines out on the web that will take a query and return it as am xlsx file. You just need to search google for them: http://letmegooglethat.com/?q=oracle+apex+export+to+xlsx
Thank you,
Tony Miller
Los Alamos, NM
-
The query joins a materialized view to several tables. The app sits on a secure network with no internet access, so we are not able to download any extensions, etc. I need something out of the box. I looked into using APEX_DATA_PARSER, but it only supports up to 300 columns.
-
Could you just use some PL/SQL to generate a text file that happens to be comma delimited?
-
Created a PL/SQL script to load data into a CURSOR, then used OWA_UTIL.MIME_HEADER, HTP.P, OWA_UTIL.HTTP_HEADER_CLOSE, and HTP.PRN to enable writing to a file.