One quick and easy way is to lock all dev accounts in prod. Or change their passwords, or as mentioned previously revoke their roles/privileges.
>>> [EMAIL PROTECTED] 01/04/02 11:22 AM >>> Thanks Kimberly, That is exactly my problem ..... I'd like to investigate this to restrict developers as well .. (yeah I know .... developers have access to production). The most protection level is to drop off developers schema's in production, but we don't want to do that. I'd surely investigate assigning the roles, but NOT making them active, so you can create the session but can't do much. I think I'll follow up this idea for the time being. BTW say I want to identify objects which are accessible to users through more than one role ... what is the quickest way to find out? I think I am writing something, but it is unnecessarily complicated. Any pointers for this will be very helpful. Thanks in advance Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gene Sais INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- 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).
