Geek Answers Handbook

Oracle Odp.Net unclear error when calling procedure in invalid package

I only have the worst nightmare to service: a silent mistake.

I called the procedure using Odp.Net inside the custom package, and the procedure call was interrupted without any exceptions (without checking) (both step-by-step debugging and the catch all clause are checked). After a long search, I noticed that the package was invalid (some failures on the server), after recompiling the package everything returned to normal (the call code was correct and unmodified).

Since it is really very simple to invalidate a package by accident in Oracle, I need to catch such an error, at least to register them for debugging.

With MS System.Data.OracleClient, an OracleException was thrown in this case, is there a way to get similar behavior with Oracle Oracle.DataAccess? Some kind of sqlnet.ora parameter? I did not find a similar problem anywhere on the net.

using the Oracle11R2 server, the last Oracle Win32..Net3.5 client.

+5
source share
2 answers

Have you tried enabling odp.net trace log?

<oracle.dataaccess.client>
  <settings>
   <add name="TraceFileName" value="c:\odpnet1.trc"/>
   <add name="TraceLevel" value="63"/>
 </settings>
 </oracle.dataaccess.client>

Maybe he will shed some kind of light?

+2
source

This is a problem with the provider. I changed ODP.NET after a similar exception. Now I am using dotConnect for Oracle and recommend that you do the same.

0
source

More articles:


All Articles