Well, you can also create a login trigger which will look into the "module" column of V$SESSION and raise an exception if that column has a value of "Toad" or "SQL*Plus". That would be much more effective then PRODUCT_USER_PROFILE. -- Mladen Gogala Oracle DBA email:mladeng@xxxxxxxxx Ext: 9787 > -----Original Message----- > From: Bobak, Mark [mailto:Mark.Bobak@xxxxxxxxxxxxxxx] > Sent: Thursday, August 12, 2004 4:55 PM > To: oracle-l@xxxxxxxxxxxxx > Subject: RE: PUP table > > > David, > > As you discovered, PRODUCT_USER_PROFILE only limits people > using = SQL*Plus as the client tool. TOAD does not look at > or care about the = contents of the PRODUCT_USER_PROFILE > table. If you want to restrict = non-SQL*Plus users from > certain activities, you'll have to revoke = privleges and > roles from the user(s). ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------