Log for procedures

Question

Hi All,
I have created some procedures for populating data into tables. those tables does not have any constarints like primary key,not null like that. those proecures are working fine.
I want know daily how many records are inserted into a table and log's ( stastics means wheather is executed sucessfully or not). where can i find. for log tracking purpose what we have to do.
In pl/sql how do we know procedure executed sucessfully or not ?
Please suggest meon this.
Regards,
venkat

Answer 1

You need a plsql package that has a message login procedure, this procedure "message_logger" will have several paramaters and overlays ie
  PROCEDURE message_logger(p_message_type IN NUMBER,
                           p_message_text IN VARCHAR2)  is
PRAGMA AUTONOMOUS_TRANSACTION;
v_proc_name varchar2(200) := 'message_logger';
BEGIN
-- in here you write to the message log table and commit the transaction, this transaction is autonomous so will not impact on other transactions.
EXCEPTION
    WHEN OTHERS THEN
      IF is_our_exception THEN
        raise_application_error(SQLCODE,
                                'Procedure:' || v_proc_name || ' Error' ||
                                get_exception_msg);
      ELSE
        ROLLBACK;
        RAISE;
      END IF;
  END message_logger;
PROCEDURE message_logger(p_message_text IN VARCHAR2)  is
BEGIN
    message_logger(gc_message_info,p_message_text);
END;The next thing you have to do is to setup a set of global message types some where, (in the spec of the package would be good) you can create these to your own design or purposes
  gc_message_ok    CONSTANT NUMBER := 1; -- process succeeded message log
  gc_message_info  CONSTANT NUMBER := 2; -- information message log
  gc_message_warn  CONSTANT NUMBER := 4; -- warning message log
  gc_message_err   CONSTANT NUMBER := 8; -- error message log
  gc_message_debug CONSTANT NUMBER := 16; -- debug message logThen comes the interesting part in each or the procedures packages, triggers etc that you want to log you add the following lines and exception trap. This will log the start of the process and also log the error.
Procedure/trigger etc .....
  v_proc_name varchar2(200) := "my_procedure etc";
BEGIN
      message_logger(gc_message_info,
                       'Procedure: ' || v_proc_name ||
                       ' started.);
.... YOU CODE IN HERE
EXCEPTION
    WHEN OTHERS THEN
        message_logger(gc_message_err,
                       'Procedure: ' || v_proc_name ||
                       ' FATAL unhandled Error:' || SQLCODE || ' Message:' ||
                       SQLERRM);
        RAISE;
  END;Now as for the structor of the message log table we use something like this
create table MESSAGE_LOG
  UNML_UID     NUMBER not null,
  RUN_NO       NUMBER,
  STAGE_NO     NUMBER,
  MESSAGE_TEXT VARCHAR2(200),
  MESSAGE_CLOB CLOB,
  REC_TYPE     VARCHAR2(32),
  UPDATED_BY   VARCHAR2(32),
  UPDATED_DATE DATE default sysdate,
  CREATED_BY   VARCHAR2(32),
  CREATED_DATE DATE default sysdate
);with a trigger to set the updated... and created... fields and get a sequence number for the unml_uid field (we use stage and run_no for odi run and stage numbers)
hope solves your question or at least helps.... there are probably hundreds of solutions to this one..
Edited by: DavidGD on Feb 9, 2009 9:11 PM
Edited by: DavidGD on Feb 9, 2009 9:12 PM