"Your tabular form probably has one or more columns displayed as select lists. The error occurs when the number of rows in one of the lists is too great and/or when the generated HTML for the displayed report row exceeds 32K. You will need to change the problem column to use a popup LOV display type or reduce the number of rows in the select list LOV or reduce the size of the displayed data for each row in the LOV."

Source: http://forums.oracle.com/forums/thread.jspa?messageID=3722079&#3722079


"I think would depend on whether or not the LOVs are dynamic - that is, they are based on values in other fields on the record. If they are simple lists that would be the same in every record, then you could construct the lists using PL/SQL in a hidden region at the bottom of the page and then use javascript to populate all of of the select lists on the page."

Source: http://forums.oracle.com/forums/thread.jspa?messageID=3901749&#3901749

"You need to reset pagination for the pages where you have your reports on. There's a process type "reset pagination" that lets you specify which pages you want to reset pagination on. You need to figure out when to best call this process, e.g. on load of your page 1, since you're not submitting page 1 but rather just link to another page."

Source: http://forums.oracle.com/forums/thread.jspa?messageID=1819376&#1819376
Note: "On Load – After Footer" works well.


An interesting article by Patrick Wolf on this subject, or more specifically the question "Is there a possibility to reset only the pagination of the detail report, when you have a master- and a detail report on the same page in an Oracle Application Express (APEX) application?": http://www.inside-oracle-apex.com/resetting-pagination-of-master-detail-report-in-oracle-apex/

"Creating a STANDARD report (non interactive) - using the CREATE PAGE wizard or the CREATE REGION wizard, after entering in the SQL, it will throw a simple error page (wwv_flow.accept) showing the error ORA-01461: can bind a LONG value only for insert into a LONG column
Workaround:
Run the same wizard with select * from dual to get the page and region created.
Once it is created - edit the region - and place the long nasty query in the region source. It will then take and work as expected."

Source: https://community.oracle.com/thread/2176773?tstart=0

When creating a new report page/region (or changing the SQL of an existing report), you can get this error:

Error creating page region.
ORA-00001: unique constraint (APEX_040200.WWV_FLOW_WORKSHEET_COLUMNS_UK2) violated

Cause: "The error came from using 2 columns of different tables without synonym" - e.g.: select r.id , r.name , a.name from table_r r join table_a a on a.id = r.a_id
Source: https://community.oracle.com/thread/881214?tstart=0