Inappropriate (?) ORA-06503 when the exception block contains raise_application

Inappropriate (?) ORA-06503 when the exception block contains raise_application_error but no return or raise http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:9549177700346422360 Hi, We stumbled upon ORA-06503 and wanted to use ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL, ERROR:5005'; to prevent developers from writing functions without a return statement. Works fine, but now we get a PLS-05005 error when the exception block doesn't contain a return or raise statement. We use raise_application_error very often in our exception blocks and a return statement afterwards would be dead code. Do we have to accept this dead code or is there a more elegant way? <code>ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL, ERROR:5005'; CREATE OR REPLACE FUNCTION foo RETURN NUMBER AUTHID DEFINER IS BEGIN RAISE NO_DATA_FOUND; EXCEPTION WHEN NO_DATA_FOUND THEN raise_application_error(-20001, 'some dynamic message that is handled by the caller'); -- RETURN NULL; -- Isn't this just dead code? END foo;</code> Hi, We stumbled upon ORA-06503 and wanted to use ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL, ERROR:5005'; to prevent developers from writing functions without a return statement. Works fine, but now we get a PLS-05005 error when the exception block doesn't contain a return or raise statement. We use raise_application_error very often in our exception blocks and a return statement afterwards would be dead code. Do we have to accept this dead code or is there a more elegant way? <code>ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL, ERROR:5005'; CREATE OR REPLACE FUNCTION foo RETURN NUMBER AUTHID DEFINER IS BEGIN RAISE NO_DATA_FOUND; EXCEPTION WHEN NO_DATA_FOUND THEN raise_application_error(-20001, 'some dynamic message that is handled by the caller'); -- RETURN NULL; -- Isn't this just dead code? END foo;</code>