jared,
Thanks for explanation. Still not convinced because of following two reasons
1) Same scenario can happen with explicit privileges as well. User A grants
ALL privileges on MY_TABLE to B without GRANT OPTION. Now B can create a
stored procedure to do DML on MY_TABLE and grant execute
Convinced or not, that's the reason, fallible as it may be.
On Thursday 26 December 2002 11:18, Shaleen wrote:
jared,
Thanks for explanation. Still not convinced because of following two
reasons
1) Same scenario can happen with explicit privileges as well. User A grants
ALL privileges on
I remember seeing another reason (I think from Tom Kyte). Roles tend to be
used for a larger number of users than system privileges. If procedures
could be created using rights from roles, every time a role was changed
(grant a new priv, disable, ...), the procedure would need to be invalidated
Shaleen,
This is done to preserve security.
User A owns a table MY_TABLE.
Role A_STUFF allows insert, select, update, delete on A.MY_TABLE.
grant insert,select,update,delete on MY_TABLE to A_STUFF;
( note that the role was not granted admin privs on the table )
User B is granted role
All,
Oracle support was able to resolve this issue for
me and I would like to share the learning. The problem was that I was unable to
create stored outline for sql executing within a stored procedure after turning
create_stored_outlines=true. Create outlines for sql satetements executing
