Oracle: Asynchronous trigger processing in Oracle

Question

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!

Answer 1

Santosh_Oracle wrote:
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?You wouldn't be able to insert into the same table in the same session so it's irrelevant. You'd have to wait for the first insert to finish first. And other sessions won't see any of those inserts until it is commited in that session first.
The behaviour i need is to allow inserts while
processing the previous "after insert" trigger,The first insert or it's firing trigger won't prevent other sessions from inserting too.
but to block trigger execution if another trigger
is still executing, i.e. to make a queue of triggers
waiting their time to fire.They are seperate transactions and you'd have to try and implement some sort of autonomous transaction to do that, but then you could end up in some sort of deadlock situation. Is there a particular reason why you need to do this?
Can Oracle provide such behaviour with triggers?
Maybe i should look for another solution?That sounds like the best plan. ;)