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

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Data auditing: triggers vs application code

Re: Data auditing: triggers vs application code

From: Jared Still <jkstill_at_gmail.com>
Date: Sun, 25 Sep 2005 12:23:45 -0700
Message-ID: <bf46380509251223793555fa@mail.gmail.com>


On 9/21/05, Sandeep Dubey <dubey.sandeep_at_gmail.com> wrote:
> 1. Create triggers on the live table. For each insert/update/delete insert a
> row in the audit table.

Strange and unexpected things can happen with audit triggers. They can fire 2+ times for the same row in the right circumstances.

See:

http://tkyte.blogspot.com/2005/08/something-different-part-i-of-iii.html
http://tkyte.blogspot.com/2005/08/part-ii-seeing-restart.html
http://tkyte.blogspot.com/2005/09/part-iii-why-is-restart-important-to.html


--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
http://www.freelists.org/webpage/oracle-l
Received on Sun Sep 25 2005 - 14:25:55 CDT

Original text of this message

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