PAWAN AHUJA

• Dec 3rd, 2006

 

Mutating trigger is trigger that is currently being modified by DML opertion.

we can resolve it by applying statement lelel trigger.

Regards

Pawan Ahuja

manikandan

• Dec 8th, 2006

 

if the trigger attempts to select or modify the table while the trigger has not completed (ie. table is in transition). then mutating trigger error occurs.

 because the table is in middle of a transaction so it causes the trigger to mutate.

you can change the trigger to statement level and apply the logic there.

vikramssheth

 Profile Answers by vikramssheth 

• Jan 30th, 2007

 

We can override this problem using temporary Table Concept.

sripri

 Profile Answers by sripri Questions by sripri

• May 8th, 2007

 

Mutating trigger has similar concept to that of deadlock. When a table is in the half way of executing a transaction and is the owner of a trigger and if the same table is accessed by the trigger somewhere else in the same time then at that instance mutating trigger occurs.

Robert

 Profile Answers by Robert Questions by Robert

• May 8th, 2007

 

To avoid Mutating trigger there are many ways. One of the best approach is to make use of the after trigger which clearly takes care of concurrency problems associated with mutating triggers .When after trigger is used only after the process of current updating is finished the next process gets processed.

RajivPrasad

 Profile Answers by RajivPrasad Questions by RajivPrasad

• May 8th, 2007

 

If a trigger body is trying to update dependent tables the best approach in this case to avoid mutating trigger errors would be to make the transactions independent and not associated with triggers which is technically called as autonomous transactions.

Palaniraman

 Profile Answers by Palaniraman 

• Dec 11th, 2008

 

Mutating trigger is trigger that is currently being modified by DML opertion. For eg.,
You created a trigger trigger1 on table1, it should fire after update for each row. And you wrote some update statement on the same table (table1) inside the trigger . When you execute the individual update stmt on table1, the trigger get fires and the trigger also is currently being updated the same rows in table1, which is called mutating error and mutating trigger.

ndrajit.raj

 Profile Answers by ndrajit.raj 

• Dec 23rd, 2008

 

Mutating table is table which is modified by any DML statement.
It is inconsistent mode and we write row level trigger to solve it.

imran44

 Profile Answers by imran44 

• Dec 27th, 2008

 

Mutating trigger is trigger that is currently being modified by DML opertion.

sabrishandyou

 Profile Answers by sabrishandyou 

• Jan 26th, 2010

 

There are cases when we have mutating table error inspite of using an "AFTER TRIGGER at ROW LEVEL".  This happens when you are using an after delete trigger.  For instance a delete was issued and the trigger gets fired.at the same time it also needs the count of the records in the table.  In such a case,it gives a mutation error.  This can be solved by make it a statement level trigger.  Because in such a case, the table count is queried after the delete is fully executed.

ASHOK

• Aug 31st, 2012

 

MUTATING :
MUTATING TRIGGER IS TRIGGER WHICH IS USED TO PERFORM DML OPERATIONS WE CAN RESOLVE BY
REGARDS
ASHOK

Code
CREATE OR REPLACE TRIGGER TRG_UPDATE_SAL


BEFORE UPDATE ON EMP


FOR EACH ROW 


BEGIN


IF :NEW.SAL<:OLD.SAL THEN


UPDATE EMP SET COMM =2000;


ELSIF :NEW.SAL<:OLD.SAL THEN


UPDATE EMP SET COMM=1000;


END IF;


END;

maxin john

• Jun 8th, 2015

 

soo...... how you are going to use that lelel trigger :O

Lokesh

• Nov 18th, 2015

 

A mutating table is a table that is being modified by an UPDATE, DELETE, or INSERT statement. The session that issued the triggering statement cannot query or modify a mutating table. If you must update a mutating table, you can bypass these restrictions by using a temporary table, a PL/SQL table, or a package variable. For example, in place of a single AFTER row trigger that updates the original table, resulting in a mutating table error, you might use two triggers—an AFTER row trigger that updates a temporary table, and an AFTER statement trigger that updates the original table with the values from the temporary table.

Habib Ali

• May 10th, 2016

 

When your DML Trigger, tries to modify the same triggering table. Then Mutating issue occurs, to resolve it
1) First try to change the PLSQL Block
OR
1) Change AFTER STATEMENT from ROW LEVEL
2) Make your PLSQL Block of code as AUTONOMOUS TRANSACTION

shaik mazhar

• May 12th, 2016

 

When table 1 is linked to table 2 with a foreign key then you will get Mutation error. The best way to avoid is to use the object oriented oracle terminology or You can avoid by using the combination of row level and statement level trigger, the above method has limitation when roll backed as PL/SQL table type will not purge the data.
So the best method is to use the combination of rowlevel trigger and GTT concept

asha

• Jul 7th, 2016

 

If You are writing a trigger after update on a x table and then writing update statement on same x_table table then It will give Mutating Error statement.

Amit Bhardwaj

• Feb 9th, 2017

 

If you are trying to access or modify the triggering table into the same trigger and that too for a row level trigger then Mutating Trigger error occurred.

adarh katiyar

• Jun 17th, 2017

 

use PRAGMA AUTONOMOUS_TRANSACTION in trigger block,
issue never comes ...