I think the best thing to do is explain potential problems with this type of access to the right people, document everyone's opinions in the matter then give them what they want and do it smartly. Create a way to kill sessions from a menu or stored procedure that logs the actions etc...so you can blame the right person when they kill the wrong session. Of course it wouldn't be too hard to exclude the background sessions from the list of possible options.
Ethan Post perotdba (AIM), epost1 (Yahoo) -------------------------------------------------------------------- -----Original Message----- Sent: Thursday, July 11, 2002 3:20 PM To: Multiple recipients of list ORACLE-L It looks like job security :) -----Original Message----- Sent: Thursday, July 11, 2002 3:47 PM To: Multiple recipients of list ORACLE-L Joe, Once you open this door, you will never get it closed. Next they will want to modify the table structures. What are you going to do thie first time they kill an Oracle Background session? I agree with Dick. Don't do it. Make them call you. Tom Mercadante Oracle Certified Professional -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Post, Ethan 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).
