It is not one of my DBA's, it's an outside vendor so I do not want to
post the code. I have actually been changing the package name as well
for that reason in my posts. They can run it on their side with no
issue using pl/sql developer. I can also run the qry that the procedure
executes using a regular cfquery call as well. It is only when I try to
run their procedure using CF that the issue arises.
Thanks,
Scott
-----Original Message-----
From: Deanna Schneider [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 14, 2004 1:48 PM
To: CF-Talk
Subject: Re: Oracle Stored Procedures
Scott,
Are you sure that it's actually returning a ref cursor? You'll get this
error if you say that you are returning one, but for some reason one is
not
returned. For example, if you have error trapping in your procedure and
the
cursor never gets opened. Therefore, if I'm returning a cursor, I always
make sure that if I've trapped errors and not opened the intended
cursor,
that I open a "dummy" cursor and return that.
(This would probably be easier to debug if your DBA's would give you the
code to the cursor. Based on the name, it looks like it's not "real"
code
anyway. Think you could talk them into it?)
> >Janet,
> >I have the snippet now from them. This is how it's currently defined
> >(which looks like it's in line with what you posted aside from In
Out):
> >
> >Type ReturnSet is ref cursor;
> >Procedure testpckg(curReturnSet Out Returnset);
> >
> >They had switched it before to be In Out for me and I still had the
same
> >error. The one thing I did notice is they do not have it defined
with a
> >schema name, they just have:
> >
> >package Test01 is
> >
> >Type ReturnSet is ref cursor;
> >
> >Procedure testpckg(curReturnSet Out Returnset);
> >
> >Could that possible cause a permissions issue as Adam had alluded
too?
>
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
