I am having the same problem. I see that there is currently no resolution to this question. Can you please tell me if/how you resolved it? Now I cannot get back into the page at all to remove the custom/alternate reports. You used to be able to manage those from within the Builder window, but I dont see them anymore in this latest version of APEX that we are running (5.1.2.00.09).
i recorded this exact issue sometimes back and i came to realize its a bug in 5.1 to i applied patch to 5.1.3 but didn't exactly resolve it - but in order to get back to your reports simple comment some columns in your query SELECT ... statement then save the changes you should be able to run the page again.
My ultimate solution regarding saved Reports is to create radio groups and split all saved reports into 3 groups and users still love it.
Thank you! Commenting out some columns worked! I thought I was going to have to re-create that whole page! That would be a lot of work!
The crazy thing is, now that I commented out some columns and saved it and then uncommented them and saved again the page works! Even with the Alternate reports. Not sure why.
the problem with IG its not fully so stable (unexpected bugs) - if you un-comment those same columns again the error will randomly popup, why cant you split the reports into 2 IGs and conditionally display them that way you only save few acceptable reports in each.
We are having the same issue.
We are working in version 5.1.2.00.09
Ours seems to not care if it is first private report or if there are more. We are thinking it has to do with the number of fields on the report rather than the number of reports.
We have found that if we export and import the page in question when it gets locked up for people they can get back into it... but that is not a good answer. I hope Oracle looks at this soon.
did you see my previous response - the work around is to create 2 or more IG (use radio buttons to add conditions) and split # of saved reports as well as # of columns rendered depending on how you implement this part users would like it.
But due to this issue i applied a patch to Apex5.1.3 that's didn't resolved it.
IG is relatively new and still has some critical issues also its architecture is so complicated to customize unlike Forms or IR.
John Snyders-Oracle - Sorry to bug you, but you are the only person I can think of that might be able to help. How can we get this elevated to a bug? Do you know if there is any workaround? It is hindering our ability to move forward with the IG. Every time I make changes to saved reports, it starts throwing this unhandled exception again. Unfortunately, we were really far along with development before we started attempting to create custom alternative reports. Now its too late for us to go back to custom apex_item reports. Can you please help us? Or point me to someone who can?
So I just searched through Oracle Support and found a document that I am sincerely hoping is the answer to this. If I am understanding the document correctly, it looks like it will be fixed in release 5.1.4.00.02.
The bug is described as follows: 26199331 : INTERACTIVE GRID: ORA-06502: WHEN REPORT METADATA EXCEEDS A CERTAIN LIMIT
Yes this sounds like the bug you are describing. apex.oracle.com is upgraded to 5.1.4 so you should try a test case out there to see if it resolves the problem. And upgrade to 5.1.4 when it becomes generally available.