Jason Tucker's Blog

not at all creative...

More Oracle .Net Provider stuff.

Whatever you do if your expecting a REF CURSOR back from an SP, make sure your REF CURSOR param's direction is set to OutPut. Atleast that's what I think is causing the provider to error out with error num -3000.

I could be wrong, it's happened once before.

Posted: Feb 26 2003, 07:10 PM by jtucker | with 2 comment(s)
Filed under:

Comments

Paul Speranza said:

Jason,

I user the MS Oracle provider and the ref cursor does have to be set as an out parm.


Paul
# February 26, 2003 5:11 PM

Brad More said:

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.

We have actually dropped back to use MSDAORA.1 for a bit after evaluting both MS and ODP.NET providers for Oracle. We are stability freaks, though. One minute of downtime is money out of our clients pockets.

We also require pretty good scalability and load capability. As a frame of reference, one of our clients using the legacy product that my webservice suite replaces processed about 490,000 transactions today.
# February 26, 2003 5:13 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)