Handling errors nicely in logoff called procedure

Question

I have a logoff trigger that calls an autonomous tx procedure which purpose is to collect program names and session stats (resource consumption) for some basic session profiling and accounting.
To catch any error that otherwise could lead to unclean logoff (and failing to collect data), this procedure has a call to ksdwrt, which dumps a trace file (and also posts to alert.log). This tracing can become a problem if there's a 'frequent' error e.g. usually a full tablespace - creating files and a couple of rows in alert.log each second or so...
I'm thinking I will remove the call in the handler, and dont know any better than to replace it with a null; call. Any ideas on how to do it differently?

Answer 1

Use an inner block to handle the exception.
CREATE OR REPLACE PROCEDURE p_mc_ips
   (lDate IN DATE)
IS
BEGIN
   FOR lrec IN (SELECT DISTINCT a.title title,b.machine_ip machine_ip
                FROM job_list a,td b
                WHERE a.jobnumber = b.jobno
                AND b.act_date = TO_CHAR(ldate,'DD-MON-YYYY'))
   LOOP
      BEGIN
         INSERT INTO net_address(p_inv,machine_ips)
         VALUES(lrec.title, lrec.machine_ip);
      EXCEPTION
         WHEN DUP_VAL_ON_INDEX THEN
            DBMS_OUTPUT.PUT_LINE('DUPLICATE RECORDS EXISTS');
      END;
   END LOOP;
   COMMIT;
END p_mc_ips;You'll have noticed that I've streamlined your code a bit. We'll save using FORALL and anti-joins for another day ;)
Cheers, APC