Re: trapping pl/sql errors with line numbers

Our customer wanted detailed info about where errors were happening in reports we were converting for them. After many iterations I am now using a package that 1) tracks the start and end times, 2) tracks which procedure/function the report is in, and the path of proc/funcs that got it there, with a call to a proc at the begin/end of the unit, 3) lets me tell what is being done, to what table, with an info msg, 4) called at top most exception handling I record a detailed msg with it that is put on the report.

If you only need info for Stored Procedures/Functions/Packages there is DBMS_UTILITY's format_call_stack and format_error_stack, but these don't seem to work in units coded in Reports or Forms.

"Jeff Smith" <jsmit234 at ford dot com> wrote in message news:bcs9ov$svi6_at_eccws12.dearborn.ford.com...
> I have been searching docs and sites but no luck.
>
> When catching unhandled errors in PL/SQL procedures using 8.1.7, is there
> any internal function that can record the line number that failed?
>
> If caught in an WHEN OTHERS THEN exception block, we record the SQLCODE,
but
> it would be nice to know what line failed. Having the line from all_source
> would make it easier to debug.
>
> Regards,
> Jeff
>
>
Received on Mon Jun 23 2003 - 10:19:57 CDT