I have a stored procedure that works just fine when testing, but
throws that "Missing right parenthesis error when I call it.

call isi.incuity.parse_external_key(1.1.1.1.1.1)

I am actually having this problem with all of my stored procedures
that I try to call. But they all work fine in testing.

And that parameter is a string.

I figured out that if I put single quotes around the string, the
missing right parenthesis error goes away.

But, now it throws ORA-06553: PLS-306: wrong number or types of
arguments in call

I even get this error for a stored procedure that doesn't even take
any parameters!

call isi.net_gap_op_log.getgapbucketsdefn()

chris.damsgard (AT) gmail (DOT) com wrote:
: I have a stored procedure that works just fine when testing, but
: throws that "Missing right parenthesis error when I call it.

: call isi.incuity.parse_external_key(1.1.1.1.1.1)
^^^^^^^^^^^^^

What on earth are you trying to pass in?

That doesn't look like any kind of parameter format with which I am
familiar.

If this works in testing then you must be using some kind of testing
interface that prompts for the parameters as I can't imagine that the
above snippet of code is what you are actually testing.

What is the signature of that procedure?

chris.damsgard (AT) gmail (DOT) com wrote:
Call? Why? This syntax is valid in Oracle but the last time I saw it
used was over a decade ago.

What is isi? Is it a schema name?
What is net_cgap_op_log? Is it a package name?
What is getgapbucketsdefn? A stored procedure?
Why aren't you providing the required parameters if you know it won't
work without them?

Run the SQL statement and post the results:

SELECT position, argument_name, data_type, in_out
FROM all_arguments
WHERE package_name = 'NET_CGAP_OP_LOG'
AND object_name = 'GETGAPBUCKETSDEFN'
ORDER BY 1;
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

isi is the schema
net_gap_op_log is the package
getgapbucketsdefn() is the procedure.

It just returns a ref cursor.

I am using call because of the software that I am trying to get the
ref cursor data into.

The other procedure I mentioned (parse_external_key) takes a period
delimited string and parses out the values for me.

So, 34.63.29.14.84.26 would parse to:

34
63
29
14
84
26

But the main problem is that I can't get that ref cursor back from
these procedures (even when no input parameters).

isi is the schema
net_gap_op_log is the package
getgapbucketsdefn() is the procedure.

It just returns a ref cursor.

I am using call because of the software that I am trying to get the
ref cursor data into.

The other procedure I mentioned (parse_external_key) takes a period
delimited string and parses out the values for me.

So, 34.63.29.14.84.26 would parse to:

34
63
29
14
84
26

But the main problem is that I can't get that ref cursor back from
these procedures (even when no input parameters).

isi is the schema
net_gap_op_log is the package
getgapbucketsdefn() is the procedure.

It just returns a ref cursor.

I am using call because of the software that I am trying to get the
ref cursor data into.

The other procedure I mentioned (parse_external_key) takes a period
delimited string and parses out the values for me.

So, 34.63.29.14.84.26 would parse to:

34
63
29
14
84
26

But the main problem is that I can't get that ref cursor back from
these procedures (even when no input parameters).

isi is the schema
net_gap_op_log is the package
getgapbucketsdefn() is the procedure.

It just returns a ref cursor.

I am using call because of the software that I am trying to get the
ref cursor data into.

The other procedure I mentioned (parse_external_key) takes a period
delimited string and parses out the values for me.

So, 34.63.29.14.84.26 would parse to:

34
63
29
14
84
26

But the main problem is that I can't get that ref cursor back from
these procedures (even when no input parameters).