How to Ensure that a new Trigger does not Screw up Existing Processes
<p>Background:</p>

<ul>
<li>We have a (very) mature legacy system that is built on an Oracle database. </li>
<li>We need to add a number of triggers that on every update, insert, or delete on a set of specified tables create a record in a table called TBL_REPLICATION.</li>
<li>Whatever happens, nothing should prevent the execution of existing functionality. </li>
</ul>

<p>What I mean by this is that if, say, there is a problem writing to TBL_REPLICATION (due to contention or whatever) it would be preferable that the action of the new trigger fail and <strong>no</strong> record be written to TBL_REPLICATION rather than any other actions be affected.</p>

<p>Is there anything that we could do - either in the triggers or in the table that they will write to  - to make the writes to TBL_REPLICATION somehow <em>less critical</em> than the existing writes and reads (on the other tables)? </p>

<p>I realise that "less critical" is rather a nebulous term but I hope I have got the gist of what I am trying to do across.</p>