Re: to check READ/WRITE permissions on directory object in 10gR2 database

From: Joey D'Antoni <jdanton1_at_yahoo.com>
Date: Thu, 12 Nov 2009 11:27:08 -0800 (PST)
Message-ID: <57510.57674.qm_at_web59002.mail.re1.yahoo.com>



I read that way too fast.. Looking deeper now.

From: Howard Latham <howard.latham_at_gmail.com> To: jdanton1_at_yahoo.com
Cc: anuragdba_at_gmail.com; oracle-l_at_freelists.org Sent: Thu, November 12, 2009 2:19:51 PM
Subject: Re: to check READ/WRITE permissions on directory object in 10gR2 database

yeah but that wont give privs on directorys or will it?

On 12/11/2009, Joey D'Antoni <jdanton1_at_yahoo.com> wrote:
> Anurag,
>
> DBA_TAB_PRIVS is still there.
>
> SQL*Plus: Release 10.2.0.4.0 - Production on Thu Nov 12 14:16:22 2009
>
> Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
>
>
> Connected to:
> Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
> With the Partitioning, OLAP, Data Mining and Real Application Testing
> options
>
> OPS$ORACLE_at_ORCL> desc dba_tab_privs
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> GRANTEE NOT NULL VARCHAR2(30)
> OWNER NOT NULL VARCHAR2(30)
> TABLE_NAME NOT NULL VARCHAR2(30)
> GRANTOR NOT NULL VARCHAR2(30)
> PRIVILEGE NOT NULL VARCHAR2(40)
> GRANTABLE VARCHAR2(3)
> HIERARCHY VARCHAR2(3)
>
>
>
>
>
> ________________________________
> From: Anurag Verma <anuragdba_at_gmail.com>
> To: ORACLE-L <oracle-l_at_freelists.org>
> Sent: Thu, November 12, 2009 2:14:24 PM
> Subject: to check READ/WRITE permissions on directory object in 10gR2
> database
>
> Hi all,
>
>
> In a 10g Release 2 database, how do I see, to which all users READ or WRITE
> permissions are granted on a particular directory object?
>
> Is there any view like DBA_TAB_PRIVS?
>
>
>
> --
>
> Anurag Verma,
> Database Administrator
> ERCOT(Electric Reliability Council of Texas),
> Texas 76574
>
>
>
>

-- 
Howard A. Latham



      
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Nov 12 2009 - 13:27:08 CST

Original text of this message