Re: Trapping Exception Messages within a PL/SQL program

From: Keith Jamieson <Keith.Jamieson_at_phoenix.ie>
Date: Thu, 4 Jan 2001 15:43:19 -0000
Message-ID: <9325rm$5c5$1@kermit.esat.net>

You can use see the error message by using the Oracle SQLERRM function. Just make sure you limit it to 255 characters.

The messages and their meanings and probable causes and solutions are all in the oracle server manual.

Frederick C. Lee wrote in message ...
>Greetings:
> I've trapped many exceptions, but rarely understand them. Passing the
>exception to the parent procedure would allow me to see some ambiguous
>ORA-number.
>
> I would like to trap or decipher the code & message of such exceptions
>and be able to either present the trapped message to the user such as via
an
>alert, or from within a stored procedure written to an *.err file for later
>review {such as from a batch process}.
>
> Also, if anyone can suggest a handbook of <all> error/exception codes
and
>their meanings...that would be great!
>
>Thanks.
>
>Ric.
>
Received on Thu Jan 04 2001 - 09:43:19 CST