Wow, ODP.NET 10.2.0.20 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.
[UPDATE]
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.