One of the little nuances that still make life annoying for DBA's. To be
able to grant access to another user's objects, you must have been directly
granted the access yourself with grant option, even if you're SYS. In this
case, you must log on as FRED, do a grant all with grant option to SYS, and
then SYS can pass the privilege on.
It annoyed me in version 7 and it still annoys me now. As a DBA you can
drop someone else's objects, but you can't grant access to someone else.
Duh! Hopefully we can soon say "fixed in the next release"!
--
HTH. Additions and corrections welcome.
Pete
Author of "Oracle8i: Architecture and Administration Exam Cram"
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!"
Bruce Pihlamae, long-term Oracle DBA
"Fim Tox" <tim_at_blueheath.com> wrote in message
news:d4e73249.0202060526.2bf59f08_at_posting.google.com...
> I've created a user fred who has his own schema.
> I've created a user joe who I want to be able to
> update/insert/delete/select any table in fred's schema.
> So.. I log in as SYS (or SYSTEM, the effect is the same) and type:
> grant update,insert,delete,select on fred.mytable to joe;
> and it complains saying:
> ORA-01929: no privileges to GRANT
> I thought SYS could do anything?
> So.. I explicitly add the GRANT ANY PRIVELEGE system privilege to SYS,
> and try again.
> I get the same result.
> What's going on??
> Help!!!!
Received on Wed Feb 06 2002 - 10:04:36 CST
