Security re: default and non-default roles

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, Received on Thu Jul 17 2003 - 08:26:07 CDT