Re: Shutdown and startup by Non dba: Question
Date: 1995/08/25
Message-ID: <stauffer-2508950927480001_at_stauffer.swarthmore.edu>#1/1
In article <41iund$pf_at_nntp.interaccess.com>, akaplan_at_psycfrnd.interaccess.com (Ari Kaplan) wrote:
-shahmiri_at_news.gate.net (Irfan A. Shahmiri) writes: -
->Hi Folks,
-
->I want the operators to shutdown and startup oracle
->and I don't want the operator account to be a member
->of the dba group.
-
My thought has been to grant the OSOPER role to my system admins so that they are able to perform startup/shutdown and recovery operations in the event that I am not on site (I'm the only DBA person).
The OSOPER roll can perform STARTUP, SHUTDOWN, ALTER DATABASE OPEN/MOUNT, ALTER DATABASE BACKUP, ARCHIVE LOG, RECOVER.
I want the system administrators to be able to do these operations, but I also want to ensure that they cannot perform any operations related to database security (new accounts/changing access/etc) and that they are unable to see the application tables and tables related to database security.
Is this a good idea? Received on Fri Aug 25 1995 - 00:00:00 CEST