Devart Forums

Hi;

We have a .NET application that is calling stored procedures in an Oracle 8i database. When the Oracle developers make changes and recompile objects/stored procedures in the database subsequent calls from our application fail and return the error "ORA... statement handle not executed." If we restart our application then everything works fine. This led us to believe that maybe we are not closing all of our connections but we reviewed our code and everything looks fine. Does anyone have any ideas as to why we have to re-start our application after changes are made on the database?

Thank you!!!


John

Connections don't close if you use connection pooling.
You can set pooling parameter to false in your connection string to disable pooling.
At the next version of OraDirect .NET we'll add a new feature of clearing connection pool by OracleConnection.ClearPool method.

Hi Oleg;

That should work; I will give it a try. However, it seems there will be a price to pay in terms of performance... I guess that is just a trade-off that we will have to live with.

Thanks!


John

Yes, disabling the connection pool corrects the issue and the performance hit does not seem too bad.

FYI You can disable the connection pool by adding the following to your connection string:

pool=false;

You've made a typo, to disable the connection pool you should add the next to the connection string:
pooling=false;

Yes, good catch - thank you for the correction!