Re: Privilege Problem

From: Thomas Kyte <tkyte_at_us.oracle.com>
Date: Fri, 13 Nov 1998 15:54:53 GMT
Message-ID: <365d54b0.95004919@192.86.155.100>

A copy of this was sent to s_teng_at_hotmail.com (if that email address didn't require changing) On Fri, 13 Nov 1998 15:07:41 GMT, you wrote:

>If I log on as that user, and issues the following SQL, I get the following
>results:
>
>SQLWKS> select * from session_roles
> 2>
>ROLE
>------------------------------
>0 rows selected.
>SQLWKS> select * from user_role_privs
> 2>
>USERNAME GRANTED_ROLE ADM DEF OS_
>------------------------------ ------------------------------ --- --- ---
>0 rows selected.
>
>As that user I can "CREATE OR REPLACE" any proc or function that already
>exists under that schema, or I can even "DROP" a func or proc, but I cannot
>"CREATE" a new one? Does this sound right?
>

from the docs:

Privileges Required to Drop Procedures and Packages

---

To drop a procedure or package, the procedure or package must be in your schema or you must have the DROP ANY PROCEDURE privilege. An individual procedure within a package cannot be dropped; the containing package specification and body must be re–created without the procedures to be dropped.

so, you need no privelege to drop your 'own' objects -- anyone can drop things they own.

Same with OR REPLACE. You need no priveleges to REPLACE your own code with some new code. If you own it, you can drop it, you can replace it.

>I know I can create the procs and funcs under another user and grant
>privileges and make synonyms, but the user currenty has reports and code that
>have the schema owner hard coded and I want minimal impact while not allowing
>the user to modify these objects.
>
>
>
 

Thomas Kyte
tkyte_at_us.oracle.com
Oracle Government
Herndon VA

--
http://govt.us.oracle.com/ -- downloadable utilities  

---

Opinions are mine and do not necessarily reflect those of Oracle Corporation  

Anti-Anti Spam Msg: if you want an answer emailed to you, you have to make it easy to get email to you. Any bounced email will be treated the same way i treat SPAM-- I delete it. Received on Fri Nov 13 1998 - 09:54:53 CST