ODP.NET

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Why would connection pooling cause problems with a trigger?

917394Feb 21 2012 — edited Feb 27 2012

This is a strange one. We have an app that deletes a row in a database table, and this table has a delete trigger on it. The row gets deleted every time the app is run, yet the trigger only fires intermittently. It's not that the trigger is failiing in some way - it just doesn't get called at all. If I issue the same delete command in PL/SQL developer then the trigger fires every time.

Several hours later and out of desparation I tried turning off connection pooling via the app's connection string, and found that the trigger now fires every time. Any ideas what might be causing this behaviour? I can reproduce/fix the issue every time simply by setting "Pooling" to true or false!

We are using Oracle 11g and ODP.Net v4.112.2.0.

Thanks in advance
Andrew

Locked Post

New comments cannot be posted to this locked post.

Locked on Mar 26 2012

Added on Feb 21 2012

#odp-net

8 comments

589 views