Asynchronous trigger processing in Oracle

From: Alex Voitik <idebeinder_at_tut.by>
Date: 9 Jul 2004 03:40:08 -0700
Message-ID: <8d0f28f3.0407090240.7530ddb7@posting.google.com>

Hi,

could anyone explain how Oracle executes triggers, namely if a trigger is fired in asynchronous mode or not? Maybe it is tuneable?

For example, there is a trigger defined as

CREATE OR REPLACE TRIGGER Convert_Transaction AFTER INSERT OR UPDATE ON TB_TRANSACTIONS FOR EACH ROW
BEGIN
--
--code which may be time-consumimg
--

END; This is the only trigger defined for the table.

Will Oracle allow inserts in the table
TB_TRANSACTIONS if the processing of trigger from the previous INSERT is not finished? If so, will the trigger for this new INSERT be fired?

The behaviour i need is to allow inserts while processing the previous "after insert" trigger, but to block trigger execution if another trigger is still executing, i.e. to make a queue of triggers waiting their time to fire.

Can Oracle provide such behaviour with triggers? Maybe i should look for another solution?

Thanks for the help! Received on Fri Jul 09 2004 - 05:40:08 CDT