Re: scheduler job_creator is DBA user account

We are fighting the same battle with hundreds of scheduler jobs created by DBAs in a database acquired via acquisition. In our case most of the jobs were owned by a single schema who's sole purpose is to host the jobs. Our solution was to script out the jobs where the job_creator != owner (using Toad or SQL Developer), then recreating them while logged in to the owner's account.

Note that if the job_creator was a DBA and has the DBA role granted to it, then either the owner will need DBA granted to it (not an optimal solution) or you will need to ensure that the owner privileges are sufficient for each of the jobs to run.

Regards,

Doug

> On March 9, 2023 at 1:53 PM Jeff Chirco <backseatdba_at_gmail.com> wrote:
>
> We have a lot of custom applications in our database all under locked schema accounts. When we create scheduler jobs, the owner is the schema but since the command gets run as a DBA account logged in the JOB_CREATOR is the DBA that ran it. Which then when you look at active sessions while the job is running it is that DBA user. Is there a way to have the JOB_CREATOR be the schema instead? We dropped a DBA account then found out that all the jobs he created for other schemas became disabled. Trying to avoid this in the future.
>
> Thanks,
> Jeff
>

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