Aren't the Discoverer EUL tables granted to PUBLIC? If the users are gone why are you not performing a drop user x? Or at the very least why not lock the user accounts then you can leave the associated privileges in place without worry the privileges will be used. ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of SHEEHAN, JEREMY Sent: Wednesday, October 21, 2009 2:02 PM To: 'jdanton1@xxxxxxxxx'; 'oracle-l@xxxxxxxxxxxxx' Subject: Re: Table Revoke Frustration!! Tried that. No such luck. ________________________________ From: Joey D'Antoni <jdanton1@xxxxxxxxx> To: SHEEHAN, JEREMY; oracle-l@xxxxxxxxxxxxx <oracle-l@xxxxxxxxxxxxx> Sent: Wed Oct 21 13:59:31 2009 Subject: Re: Table Revoke Frustration!! Jeremy, Can you do an 'alter session set current_schema=$EUL_SCHEMA' and then issue the revokes? Joseph D'Antoni Synthes USA ________________________________ From: "SHEEHAN, JEREMY" <JEREMY.SHEEHAN@xxxxxxxxxxxxxxxxx> To: "oracle-l@xxxxxxxxxxxxx" < > Sent: Wed, October 21, 2009 1:49:04 PM Subject: Table Revoke Frustration!! Hey all, I'm working on a little something where I need to revoke all access given to users that are no longer with the company. Roles are no problem. I keep on having issues with tables, though. We use Discoverer and privs are granted directly to the users on EUL tables. I keep on getting the "ORA-01927: cannot REVOKE privileges you did not grant" error. I expected this. However, why is it that I can revoke these privs through OEM Grid Control and not via a simple procedure run in SQL Plus (conneted as the same user)? Any ideas? RDBMS - 9.2.0.8 OS - AIX 5.3.9 Thanks in Advance! Jeremy P Consider the environment. Please don't print this e-mail unless you really need to.