Solve Your Every Day Technical Problem

ORA-04091: table XXXX is mutating, trigger/function may not see it and you want to get around that. This short article will describe and demonstrate the various methods of getting around the mutating table error. If you are interested in why you are getting it and in what cases you will get it, please see the Oracle Server Application Developers Guide (click here to read it right now -- this link is to technet.oracle.com.  You need a password to access this site but you can get one right away for free). Avoiding the mutating table error is fairly easy.  We must defer processing against the mutating or constrainng table until an AFTER trigger.  We will consider two cases: Hitting the ORA-4091 in an INSERT trigger or an UPDATE trigger where you only need access to the :new values Hitting the ORA-4091 in a DELETE trigger or an UPDATE trigger where you need to access the :old values Case 1 - you only need to access the :new values This case is the simplest. ...