994927 wrote:Properly implemented procedures won't throw errors.
How can I catch the errors occurred in sessions (defined by Module and Service names)?
I used DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE, but it caught only the statements that worked.
Oracle 11g R2
Windows 2008 64-bit
Thanks in advance
994927 wrote:Oracle is VERY GOOD at reporting the which SQL statement failed & why it failed;
I have an application which got error from Oracle on a specific action.
The developer of that application wants to know what statement Oracle failed on.
Hemant K Chitale wrote:Trace file also have syntax errors; I have just tested the following with 188.8.131.52 on Windows.
It depends on the type of the error. Syntax and Parse errors won't appear in the trace file because they aren't database errors.
In trace file:
SQL> exec dbms_monitor.session_trace_enable; PL/SQL procedure successfully completed. SQL> select y from dual; select y from dual * ERROR at line 1: ORA-00904: "Y": invalid identifier
PARSE ERROR #327830808:len=19 dep=0 uid=84 oct=3 lid=84 tim=7826182168 err=904 select y from dual WAIT #327830808: nam='SQL*Net break/reset to client' ela= 7 driver id=1111838976 break?=1 p3=0 obj#=-1 tim=782 6182711 WAIT #327830808: nam='SQL*Net break/reset to client' ela= 114 driver id=1111838976 break?=0 p3=0 obj#=-1 tim=7 826182926 WAIT #327830808: nam='SQL*Net message to client' ela= 2 driver id=1111838976 #bytes=1 p3=0 obj#=-1 tim=7826183 038