Help on error trapping

From: Tom Deseamus <tdeseamus_at_digital-hire.com>
Date: Fri, 7 Jan 2000 08:24:38 -0800
Message-ID: <PGmd4.10798$Ak.141437_at_news1.mia>

[Quoted] [Quoted] I'm trying to develop an exception handler that I could use to check on actual error numbers and supply my own error messages. Here's the code, any suggestions?

[Quoted] PROCEDURE EXEXCEPTIONHANDLER(DANUMBER NUMBER, DATEXT VARCHAR2) IS THENUMBER NUMBER;
TEXTSTUFF VARCHAR2(5);
THEERRORNUMBER NUMBER; BEGIN
 THENUMBER := THENUMBER / DANUMBER;
 TEXTSTUFF := DATEXT * 5;  DBMS_OUTPUT.ENABLE; EXCEPTION
  WHEN TOO_MANY_ROWS THEN
   DBMS_OUTPUT.PUT_LINE('TOO MANY ROWS ERROR OCCURRED');
--WHEN wrong_number_or_types_of_arguments THEN;
    --DBMS_OUTPUT.PUT_LINE('ARGUMENT CALL MISMATCH');
--WHEN NUMERIC_OR_VALUE THEN

    --DBMS_OUTPUT.PUT_LINE('NUMBER ERROR');   WHEN DUP_VAL_ON_INDEX THEN
   DBMS_OUTPUT.PUT_LINE('DUPLICATE VALUE ON INDEX');   WHEN INVALID_NUMBER THEN
   DBMS_OUTPUT.PUT_LINE('INVALID NUMBER ASSIGNMENT');   WHEN VALUE_ERROR THEN
   DBMS_OUTPUT.PUT_LINE('TRUNCATION OR CONVERSION ERROR');
[Quoted] --WHEN SQLCODE := -6512 THEN ***********************************HERE!
    --DBMS_OUTPUT.PUT_LINE('MY OWN ERROR MESSAGE');   when others THEN
   DBMS_OUTPUT.PUT_LINE('THE ERROR IS!: ' || TO_CHAR(SQLCODE)); END; Received on Fri Jan 07 2000 - 17:24:38 CET