No, it is a bit confusing, but I'll try: Bob in Chicago logs in to the database as USER_A and tries to execute USER_B.procedure and fails. Fred in Chicago logs in to the database as USER_A and tries to execute USER_B.procedure and it works. Mary in Phoenix logs in to the database as USER_A and tries to execute USER_B.procedure and it works. I have started to suspect that there is something funky with Bob's computer. I have asked him to log in to Fred's computer as himself and try there. Note, I have had Bob do a tnsping and compared it to Mary's and they are both connecting to the same database. On Fri, Feb 22, 2008 at 6:04 AM, Mercadante, Thomas F (LABOR) < Thomas.Mercadante@xxxxxxxxxxxxxxxxx> wrote: > Stephen, > > 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? > > Tom > > ------------------------------ > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Mercadante, Thomas F (LABOR) > *Sent:* Thursday, February 21, 2008 2:05 PM > *To:* andert@xxxxxxxxx; Oracle L > *Subject:* RE: Some people can't execute a procedure > > Stephen, > > Do you get an error message when the 2nd person tries to execute the > package? Or does the screen freeze? > > What do you mean? > > Tom > > ------------------------------ > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *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 in. > 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? > > >