I was trying to create a sample set of scripts to show you how to replicate it. I couldn't reproduce the issue
I noticed that I face this problem for only 1 specific user's package. I can replicate this issue in every database the package resides in. It works fine for other objects.
I don't know what is wrong. Thanks for your response, Jeff.
1 person found this helpful
What is schema name, package name, and procedure name? I'm able to reproduce the problem in combination of names like this:
CREATE OR REPLACE PACKAGE hr.hr_pack AS
That's it! I have a similar pattern.
After running the scripts below, if you login as user_a, you'll be able to replicate it.
DROP USER user_a CASCADE; DROP USER user_b CASCADE; CREATE USER gfa IDENTIFIED BY asdfasdf; GRANT resource TO gfa; CREATE USER user_a IDENTIFIED BY asdfasdf; GRANT connect TO user_a; CREATE OR REPLACE PACKAGE gfa.gfa_calc AS PROCEDURE proc; END gfa_calc; / CREATE OR REPLACE PACKAGE BODY gfa.gfa_calc AS PROCEDURE proc AS BEGIN NULL; END; END gfa_calc; / grant execute on gfa.gfa_calc to user_a;
Bugged and fixed for 19.2.