System instability using reports that raise an exceptions

Question

I am having a problem with some reports when I use the type "PL/SQL function body returning SQL query".
If the Function raise an exception, the apex's engine will call again the function and it raise again the exception. These will make a loop that doesn't end until you close the session. The problem is that this page consume all the recourse of the CPU and/or fill the partition where the logs are saved. All these generate Instability on the server and also could bring down the server.
To reproduce this error you have to follow this steps:
1)     First create a simple function to return a raise.
FUNCTION DORTEGA_TEST_RAISE RETURN VARCHAR2 IS
BEGIN
DECLARE
A NUMBER;
BEGIN
A := 12/0; --This operation generate an exception.
END;
RETURN 'SELECT 1 FROM DUAL';
EXCEPTION
WHEN OTHERS THEN
RAISE;
END;
2)     Create a empty page with one report region.
3)     Edit the report region and set these values:
a.     Type = SQL Query (PL/SQL function body returning SQL query)
b.     Display Point = Page Template Region Position 2
c.     Source = BEGIN RETURN DORTEGA_TEST_RAISE; END;
Use Generic Column Names (parse query at runtime only)
4) When we run the application the page never load, and if you look the data base, you can view that the session it’s growing and it’s begins to consume all the memory and the processor of the server.
I am using APEX 3.1.0.00.32. And the DB is 11g.
Someone know why is this happening? Are there any fix for this bug?

Answer 1

Hi:
I was able to reproduce this in APEX 3.1.2 installed in an Oracle XE instance.
The APEX engine does seem to go into an endless loop and the server Oracle process handling this request eventually does with an out-of-memory error.
However, if instead of raising an exception in the exception handler of the function I have a statement like 'Return Null;' then the APEX engine comes back with an expected response of
failed to parse SQL query:
ORA-00900: invalid SQL statement
Varad