Jason Tucker's Blog

Re: More Oracle .Net Provider stuff and another item..

 Brad More writes :

Hmm, interesting. My observation was that I got 3000 error only under load. The tests that my team ran seemed to indicate that onesies and twosies worked reasonably consistently, but when loaded up w/ ACT & WinRunner with several concurrent users, things went to hell.

And your probably correct, after doing some more research ( unfortunately groups where not much help ) on oracles forums for ODP.Net I've noticed that the -3000 error is due to a few different things which most seemed centered around connection pooling. For a bit there I was getting a little worried about scrapping the provider, since there are several leads that I followed that pointed to the fact that there will be a patchset for the provider. I sure hope I don't run into the load test issues you did, the OLEDB drivers drew too much resource..

Oh and also, has anyone seen where there is no data returned from the provider to a datareader yet when I use a dataset I get data?! I maybe posting this one on the forums.