Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Proving PL/SQL trigger firing sequence

Re: Proving PL/SQL trigger firing sequence

From: Karsten Farrell <kfarrell_at_belgariad.com>
Date: Tue, 10 Jun 2003 15:39:18 GMT
Message-ID: <MPG.194f9b80e66404a19897be@news.la.sbcglobal.net>


rs_arwar_at_hotmail.com said...
> sharkmouth_at_hotmail.com (Saul Garcia) wrote in message news:<8742cd9.0306070924.53444312_at_posting.google.com>...
> > Hi All,
> >
> > Is there an open PL?SQL code which can be used to show the sequence
> > of trigger firing with all possiblilites? That is for UPDATE, INSERT,
> > DELETE at statement level, before and after at row level. Thanks,
> >
> > Saul Garcia
>
>
> It's called debugging with dbms_output package. Goto
> http://tahiti.oracle.com and search for dbms_output.
>
> Regards
> /Rauf Sarwar
>

One small, additional comment: using the dbms_output package will not be very useful if your session cannot see output displayed from the trigger. For example, if you have a background sql job that causes the trigger to fire, then stdout won't be defined. And some scripts redirect stdout to a file (or worse, to /dev/null). You can ALWAYS write debug info to an "audit" table from the trigger, whether foreground or background, and query it later.

-- 
/Karsten
DBA > retired > DBA
Received on Tue Jun 10 2003 - 10:39:18 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US