Re: fine grain access control + partitioned table

"G.Ong" <onggs_at_acslink.aone.net.au> wrote in message news:<_IS28.6774$N31.291765_at_ozemail.com.au>...
> Hi,
>
> Our system is 8.1.6.3 on Solaris 2.7.
> We came across this pecularity:
>
> A policy is placed on a partitioned table; the predicate returned is 1=1 or
> 2=1 (to simplify discussion).
> If I perform this query:
>
> select count(*) from table_x partition (part_1) ;
>
> the explain plan shows that all partitions are scanned. The execution took a
> long time. The concern is that if I truncate a partition, it may truncate
> the whole table!!
>
> Have anybody come across this ?
>
> TIA,
> Ghee

My understanding is predicate does not apply to any DDL operations, that is any DDL you perform, the predicate is not imposed. So you probably want to separate object owner from SQL executors.

All users should be revoked with all DDLs against the objects and DDL should only be executed by the table owner and of course, you do not impose the predicate to the table owner. Received on Mon Jan 21 2002 - 16:48:34 CST