Re: Question on job-system access in OEM

From: Dave Herring <gdherri_at_gmail.com>
Date: Fri, 19 Jul 2019 14:06:04 -0500
Message-ID: <932b9e04-e29f-4ba8-b245-e1d984e3b479_at_getmailbird.com>



The issue is with permissions/access to the OEM Job scheduling system, not database / DBMS_SCHEDULER.

I believe I found a potential solution - create a role under Setup -> Security -> Role, then on each Job update to allow access by this role, then lastly grant this role to each Administrator as I create them (well, do for one and everyone else is a "Create like").

If there's a better way (other than retro-fitting the existing environments to NOT create and schedule all OEM jobs as SYSMAN) by all means share.  Thx.

Dave
On 7/19/2019 1:23:13 PM, Mladen Gogala <gogala.mladen_at_gmail.com> wrote: Version 12.1.0.4? I seem to be a bit behind the latest development. What’s going to happen next? Someone will invent a telephone with a camera which can connect to Internet? However, try granting your admins SCHEDULER_ADMIN role and CREATE JOB and MANAGE SCHEDULER privileges. That should allow the newly minted admins to perform administrative functions on DBMS_SCHEDULER. Regards

On 7/19/19 1:57 PM, Dave Herring wrote:

I've got a bit of a newb question related to view-access of other admin's jobs in OEM. The environment is 12.1.0.4 where all target jobs are created under SYSMAN account. I'd like to grant a new slew of admins the ability to view these jobs, both the definition in the Job Library along with scheduled and execution history. I don't see anything that explicitly grants this during Administrator creation so perhaps I'm missing something. Is it possible to do this?

Thx.

Dave

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jul 19 2019 - 21:06:04 CEST

Original text of this message