Re: granting another users tables ?

Bo Bell (bob_at_indigoddb.be.statoil.no ) writes:
>

 [snip]
> Although i'm able to create a table in anoter schema, I can't grant
> object rights on the tables to other users (Yes, i'm running the
> script as system (have tried internal and sys also))
 [snip]
> My only solution so far is to grant the schema owner CONNECT
> privilige, connecting as this user and granting all object priviliges
> to a DBA role. At this point the SYSTEM account may grant these
> priviliges to others.
>
Ohhhh, nooooo. This was one of the biggest DBA frustrations at v5 and v6: DBA can create/drop an object, but can't administer it, although he can backdoor into the owner's schema and give himself the ability to do so. I'd thought that v7 overcame this, since the DBA role has SELECT/UPDATE/INSERT/DELETE/REFERENCES ANY TABLE WITH ADMIN OPTION but had not tried it out. Now that I've seen this posting, I can read the doc to say that this gives the DBA the ability to grant a user the ability to, say,
SELECT ANY TABLE
but not to grant the ability to select a specific table belonging to another user/schema unless the same old workaround is used. Grrrrrrrr.

W.C. Epperson
Senior Systems Engineer
DBA Emeritus
Va. Dept. of Education Received on Wed May 24 1995 - 00:00:00 CEST