RE: Some people can't execute a procedure
Date: Fri, 22 Feb 2008 08:04:30 -0500
I want to better undertand this.
You say that User_A logs in and can execute a procedure owned by User_b. User_C logs in and User_A can no longer execute the procedure, correct? And then User_D logs in and User_A can now execute the procedure?
The only way that I can think of this happening is that execute privs are being revoked and granted on the fly by some background (trigger) process.
Is there anything specific in the Procedure to do this?
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mercadante, Thomas F
Sent: Thursday, February 21, 2008 2:05 PM To: andert_at_gmail.com; Oracle L
Subject: RE: Some people can't execute a procedure
Do you get an error message when the 2nd person tries to execute the package? Or does the screen freeze?
What do you mean?
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Stephen Andert
Sent: Thursday, February 21, 2008 1:56 PM To: Oracle L
Subject: Some people can't execute a procedure
USER_A cannot execute a procedure owned by USER_B when one person logs
USER_A can execute a procedure owned by USER_B when a different person logs in.
One person is in one city and the other is in a different city, but in TOAD, both users can "see" the procedure when browsing the procedures of USER_B. Furthermore, this is only the case in one environment (DEV) and works normally in other environments (i.e. QA)
I have confirmed (in TOAD and SQL*Plus) that USER_A has EXECUTE privs on the procedure granted by USER_B.
Help. What else can I try?Received on Fri Feb 22 2008 - 07:04:30 CST