Heres something interesting. One of my developers just came to me with
an error he is getting on a certain function in a certain package. It
was the same 'wrong number/type arguments' error.

The weird part was that only he would get it. If I logged into the
application and viewed the same page... it worked fine. (We use oracle
user accounts, no global account).

I checked permissions and roles and everything seems dead on. No
difference in his account from another developer's or mine.

So after a few minutes of going over every single line of code... it
got it to work for him. Once I changed the case of the schema name it
worked. So basically the schema name was case-sensitive..... but only
for him!

Schema names are _not_ case sensitive. If I have an account named
ADROCK, I cannot create one call adrock. Which is what makes this
issue so curious. (All the DBAs have left for the day so I haven't
gotten thier take on it)

I'm beginning to think that the "Wrong number / types arguments" error
is the DataDirect driver's general oracle error message. If anything
happens that it can't explain, it throws that error. I don't see how
this error could have anything to do with the case-sensitive schema
name. The only way it could is if there was another schema that was in
lower-case (which is impossible), with the same package, and the same
procedure.

If the schema names were case sensitive then I should have gotten an
error that says "Schema doesnt exist or you do not have access to it."

I beginning to think "Wrong number / types arguments" is to Oracle
drivers as "JRun Connection Error" is to Java. Completely non-descript
and misleading.

-Adam

----- Original Message -----
From: Scott Mulholland <[EMAIL PROTECTED]>
Date: Fri, 17 Sep 2004 10:24:29 -0400
Subject: RE: Oracle Stored Procedure - another shot, now with procedure code
To: CF-Talk <[EMAIL PROTECTED]>

Janet,
Thanks for your help.  I just upgraded one of our servers to 6.1 (the
box I was using was just MX) and it worked with no issue now.  Looks
like it was a driver version issue.

Thanks again for all your help with this, it is greatly appreciated!

Scott

-----Original Message-----
From: Janet Schmitt [mailto:[EMAIL PROTECTED]
Sent: Friday, September 17, 2004 8:38 AM
To: CF-Talk
Subject: RE: Oracle Stored Procedure - another shot, now with procedure
code

Scott -

There is nothing wrong with your code.  I recreated your CF code and
Oracle
package, etc... in our environment (CFMX, Oracle 8.1.7) and it works
just
fine.  To solve this, I would look at two things:

1.  The Oracle drivers you are using in your CF data sources.

2.   If there is more than one version of the TEST01 package and you are

not calling the version that you think you are calling.  To do this, I
would verify that you are connecting as the same Oracle user via the CF
data sources that you are connecting with when you are running the
procedure from SQL*Plus.

HTH.

Janet.

At 01:37 PM 9/16/2004 -0400, you wrote:
>Thanks to all who have offered advice thus far.  I have since been able
>to get this running in SQL plus, but still get the same error in CF.
>(MX, Enterprise edition, using default Oracle driver)
>
>
>Error received: [Macromedia][Oracle JDBC Driver][Oracle]ORA-06550: line
>1, column 7: PLS-00306: wrong number or types of arguments in call to
>'TESTPCKG' ORA-06550: line 1, column 7: PL/SQL: Statement ignored
>
>
>CF code used:
><cfstoredproc procedure = "schema.test01.testpckg" dataSource = "#ds#">
>     <cfprocresult name="rs">
></cfstoredproc>
>
>
><cfdump var="#rs#">
>
>
>PACKAGE CODE:
>
>
>package test01 is
>
>Type ReturnSet is ref cursor;
>Procedure TestPckg(curReturnSet Out Returnset);
>Procedure TestPhn(curReturnSet Out Returnset);
>end test01;
>
>
>package body test01 is
>
>   Procedure TestPckg(curReturnSet out Returnset) As
>
>
>   Begin
>     open curreturnset for
>       select name
>         from allNames
>         where (ludate between to_date('20040801','YYYYMMDD') and
>to_date('20040901','YYYYMMDD'))
>            or (insertdate between to_date('20040801','YYYYMMDD') and
>to_date('20040901','YYYYMMDD'));
>    End;
>
>
>   Procedure TestPhn(curReturnSet Out Returnset) As
>
>
>   Begin
>     open curreturnset for
>       select phid, areacode, phonenumber
>         from allPhones;
>   End;
>
>end test01;
>
>Anyone spot anything wrong with the package/procedure that could cause
>this?
  _____________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to