Geeks With Blogs

The Life and Times of a Dev Yes, we're really that weird

Wow, ODP.NET is not horribly stable yet.

I'm having the following problems:

1.  Data provider internal error(-3000) [System.String]
2.  Random connection dropping without reseting the Connection State

Only way to deal with #2 is to dispose of the connection and try again, which seems to work most of the time.  I'm connecting to a 10g running on Suse 10.1 in a virtual server, which slows disk IO, which seems to give Oracle grief.

Item #1 is more fun.  I've been able to track it to it saying that a sequence doesn't exist (probably something to do with a trigger), however, when I get that exception, it causes a memory protection fault and forces the app to exit.  Nice.  Another symptom is that it only happens when when I'm using TransactionScope.  If I use OracleConnection.BeginTransaction() I get the correct message.  Of course that message is useless--it'd be nice to know what sequence doesn't exist so that I can fix it . . .

What a pain.


The -3000 error message seems to occur when I've got bad SQL going into Oracle and then try to rebuild the OracleConnection.  Looks like I need to actually look at the error number being thrown by Oracle and not rebuild if it's bad sql.

Posted on Tuesday, October 31, 2006 10:26 AM Work | Back to top

Comments on this post: ODP.NET and it's stability.

# re: ODP.NET and it's stability.
Requesting Gravatar...
Hi, I am currently encountering the same problem as what u have describe in #1. Have you managed to find a work around? it would be nice to see what error is actually thown by Oralce, have you find a way to retrieve that information?


Left by PX on Mar 22, 2007 8:20 AM

# re: ODP.NET and it's stability.
Requesting Gravatar...
What's going on with number 1 is that you're actually getting an exception about a failed SQL call and not bailing at that point. If you then try to call ANY sql statements on the connection after you've had a bad one, you'll get this error. Only thing to do is dispose of the connection, reconnect, and then call again.

The real solution is to fix the bad SQL call.
Left by Robert May on Mar 22, 2007 8:30 AM

# re: ODP.NET and it's stability.
Requesting Gravatar...
The error #1 only occurs if you put all params in connection string. If you use the params in tnsnames.ora if works fine.
I'm using transaction scope too.
Left by Eduardo on Nov 08, 2007 11:50 AM

Your comment:
 (will show your gravatar)

Copyright © Robert May | Powered by: