RE: Unable to grant permissions to table - 7.31 HP-UX 11.0
Check the ownership of table 167. Perhaps it is not owned by the person
granting or revoking?
Scott
> ----------
> From: Art S. Kagel[SMTP:kagel@bloomberg.net]
> Reply To: kagel@bloomberg.net
> Sent: October 16, 2000 3:18 PM
> To: informix-list@iiug.org
> Subject: Re: Unable to grant permissions to table - 7.31 HP-UX 11.0
>
> Try granting the individual permissions:
>
> grant select on table167 to public;
> grant update on table167 to public;
> grant index on table167 to public;
> grant delete on table167 to public;
> grant insert on table167 to public;
> grant alter on table167 to public;
> grant references on table167 to public;>
> Rus Ambler wrote:
> >
> > Hey all,
> >
> > Not expecting much of a solution, more of a 'anyone else experienced
> this?'
> > to this poser:
> >
> > Consider the following two SQL blocks.
> >
> > select * from systabauth where tabid = 188;
> > revoke all on table188 from public;
> > select * from systabauth where tabid = 188;
> > grant all on table188 to public;
> > select * from systabauth where tabid = 188;> >
> > select * from systabauth where tabid = 167;
> > revoke all on table167 from public;
> > select * from systabauth where tabid = 167;
> > grant all on table167 to public;
> > select * from systabauth where tabid = 167;> >
> > If I run block one, I get the following expected results:
> >
> > grantor grantee tabid tabauth
> > informix public 188 su-idxar
> >
> > grantor grantee tabid tabauth
> >
> > grantor grantee tabid tabauth
> > informix public 188 su-idxar
> >
> > If I run block 2. I get the following unexpected results:
> >
> > grantor grantee tabid tabauth
> > informix public 167 su-idxar
> >
> > grantor grantee tabid tabauth
> >
> > grantor grantee tabid tabauth
> >
> > I did various tests and confirmed that all tables with a tabid less than
> 188
> > all failed to have permissions granted.
> >
> > Exporting the DB, dropping it, modifying the import SQL with the
> appropriate
> > GRANTS, and then importing also failed. Try as I might, I am currently
> > unable to grant the permissions required to PUBLIC (or to any other user
> for
> > that matter).
> >
> > I've checked for any triggers etc. but can find nothing that would
> explain
> > this.
> >
> > My only solution so far was to grant the DBA role to the user in
> question
> > (fortunately there is only one user who needs access to the DB).
> >
> > ------------------------------------------------------------------------
> > Rus Ambler
> > Fourgee Aracs
> > London, UK
> >
> > Please replace " at " with an @ when replying via email.
>