I am 99.99% sure that this is a privilege issue.
Does the user executing the procedure own it, or is it in another schema?
Larry
On 3/20/07, Hendry [EMAIL PROTECTED] wrote:
Just tried it, and it still produce the same error.
Regards,
Hendry
Clinton Begin wrote:
Try specifying the owning
Nope, the user owns it, and it is in the same schema. I've also tried
calling it using plain jdbc connection, and it works.
Regards,
Hendry
Larry Meadors wrote:
I am 99.99% sure that this is a privilege issue.
Does the user executing the procedure own it, or is it in another schema?
Larry