In an attempt to enhance security, we set up one role which is a default and has only select privileges on tables and another role, with is not default, which has update, insert, delete, as well as select privileges. Our application turns on the non-default role via set role.
This all works just fine in our development database, but not in the test database (or production). The symptom is that the non-default role is enabled on login to sql*plus, even when it's not supposed to be. Can anybody give me a clue as to where to look to find out what's wrong and fix it? TIA, Leslie -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tierstein, Leslie INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
