Re: trapping pl/sql errors with line numbers

I don't allow "ungraceful" exits.

It is unhandled in the sense that I didn't expect it. I catch the error, record and the caller handle what to do next. It would be nice to be able to get details of what the problem is.

I write good code and work hard to do so, but I don't pretend to not run into problems from time to time.

Jeff
"Martin Burbridge" <pobox002_at_bebub.com> wrote in message news:Xns939FCCAFC953Fpobox002bebubcom_at_204.127.204.17...
> "Jeff Smith" <jsmit234 at ford dot com> wrote in
> 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
> >
>
> If you remove the when others exception the calling program, java,
sqlplus,
> etc gets the full error and line number at which it occurs. If you don't
> expect the error why would you attempt to handle it?
>
> --
> Martin Burbridge
Received on Fri Jun 20 2003 - 07:22:48 CDT