Re: limiting access

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Mon, 1 Jun 2015 06:06:17 +0100
Message-ID: <CABe10sZDfrq6Qb4bEyv8jFT3_bZDt_cBSVE0j1sfPd0iRdFUwg_at_mail.gmail.com>

The obvious thing to employ would be sudo. For the two items you've mentioned it would of course also be possible to implement EM12c and corrective actions.
On 29 May 2015 15:43, "Chris King" <ckaj111_at_yahoo.ca> wrote:

> Hi All! Happy Friday!
>
> There's a plan afoot at my company to have me (the DBA architect/builder)
> pass along the monitoring of production systems to our on-call folks. Very
> good! Unfortunately, none of them have any DBA knowledge, and I've built a
> rather complex RAC setup. I'll be training them before any hands on work,
> and want to limit their access as much as possible to the linux systems and
> the oracle database. I'll want them to be able to add datafiles to
> tablespaces and restart dbconsole if it goes down, among other things.
> Linux access as oracle and possibly grid will be needed..
>
> What would you recommend as an overall method of granting the least
> possible privileges on the linux side? For instance, to restart dbconsole
> will require login as oracle, which I'd rather avoid giving away, but not
> sure that's possible.
>
> May I have your thoughts? Thanks!
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Jun 01 2015 - 07:06:17 CEST