I've just surfed via Christian Antognini
blog and found the fact of perfomance issue(CPU overhead) with triggers on Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 (64-bit) Solaris 10 (SPARC) due to Oracle bug. In the example, for reason of integrity constraint each table has its own trigger even it doesn't support any integrity (check example by the link above). "Firing blank rounds" cause increasing of CPU usage.
Out of bugs i would add a comment:
In addition, DML operations inside the triggers could lead to large number of row-level exclusive locks for large number of tables (trigger's shower). More over it's usually very hard to predict how many triggers will be fired due to some system operations when triggers realize some bussiness rules and their execution depends on the exact case.
3 comments:
I agreed with you on the point of DML operations. It operations inside the triggers could lead to large number of row-level exclusive locks for large number of tables. It is too useful on the purpose of security.
I didn't have faced this bug yet so is not sure how to resolve or handle it. As you have highlighted that there is a bug in the latest release I will definitely try to find a solution to this problem. Thanks for the updates.
I didn't have faced this bug yet so is not sure how to resolve or handle it. As you have highlighted that there is a bug in the latest release I will definitely try to find a solution to this problem. Thanks for the updates.
Post a Comment