By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,236 Members | 1,351 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,236 IT Pros & Developers. It's quick & easy.

Unable to grant execute privilege (Urgent)

P: n/a
I 'recreated' a stored procedure.

Earlier, i had given privileges to a particular group but now (after
rebuilding) when I try to grant execute privilege for the SP to the same
user group, it gives me the below message.
Any clues on this??

[IBM][CLI Driver][DB2/AIX64] SQL0458N In a reference to routine
"SITSCHM.SP_ERND_PREM" by signature, a matching routine could
not be found. SQLSTATE=42883


Explanation:

In a reference to function, method, or stored procedure
"<routine-name>" by signature, no matching function, method, or
stored procedure could be found.

If a data type is used that can accept a parameter, then the type
parameter is optional. For example, for CHAR(12), you can either
specify the parameter (CHAR(12) or omit it (CHAR()). If you
specify the parameter, then the DBMS will only accept an exact
match on the data type AND the data type parameter. If you omit
the parameter, then the DBMS will accept a match on data type
only. The CHAR() syntax provides a way to tell the DBMS to ignore
data type parameters when finding a matching function.

Note also that in the DROP FUNCTION/PROCEDURE and COMMENT ON
FUNCTION/PROCEDURE statements, an unqualified reference is
qualified with the statement authorization ID, and this is the
schema where the problem can be found. In the SOURCE clause of a
CREATE function, the qualification comes from the current
function path. In this case, there is no matching function in the
entire path.

A function cannot be sourced on the COALESCE, NULLIF, NODENUMBER,
PARTITION, RAISE_ERROR, TYPE_ID, TYPE_NAME, TYPE_SCHEMA, or VALUE
built-in functions.

The statement cannot be processed.

User Response:

Possible responses include:

o Changing the function path to include the correct schema.

o Removing parameters from the specifications of data types.

o Using a SPECIFIC name to refer to the function or procedure
instead of a signature.

sqlcode : -458

sqlstate : 42883
Oct 19 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Solved it!!
Had built the procedure in Development Center.
But did not drop the procedure from Control Center. So, this is what I
did:
dropped the procedure from control center.
Rebuilt the SP in Dev Center.
Granted the privileges thru CC.

However, I would be happy to know the reason for this strange behaviour if
anybody knows it.

Cheers,
San.

Oct 19 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.