On Wednesday, February 20, 2013 11:06:30 PM UTC-7, Lokesh ND wrote: > > Hi All, > Greetings... > > > I am new to this Group , I am learning more things from this group , i > thank all of them who are sharing there knowledge and experience in this > group . > > I would like to ask all the senior's & Member's in the group i am not > able to understand Mutating table Error Concept and steps to overcome > this error . > > > Thanks & Regards, > Lokesh > >
A mutating table error is reporting that the current transaction is trying to read from and insert into/update the same table at the same time (basically speaking). This is usually encountered in triggers that attempt to update the same table that fired the trigger due to an insert/update/delete. 11.2 offers compound triggers that can be used to 'get around' that error: http://dfitzjarrell.wordpress.com/2012/06/15/compound-interest/ You may also be able to use an autonomous transaction to circumvent the 'mutating table error' but it isn't a good practice as you lose the rollback if the trigger fails or the 'parent' transaction is rolled back (the insert/update/delete which fired the trigger in the first place). David Fitzjarrell -- -- You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to oracle-plsql-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en --- You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To unsubscribe from this group and stop receiving emails from it, send an email to oracle-plsql+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
