Re: scheduler job_creator is DBA user account
Date: Thu, 9 Mar 2023 15:34:04 -0600
Message-ID: <CAP79kiRDjj6jpRrjfaDTA7ngyd5OcCdfGpQ7E0fVQGdmwd+tpQ_at_mail.gmail.com>
Use a proxy account:
ALTER USER <APP USER> grant connect through <DBA USER> ;
Then when you connect , you connect as:
DBA_USER[APP_USER]/DBA_USER_PASSWORD (where the account you're actually
logging into is the "APP_USER" inside the brackets.
Then any operation you run is run as the APP_USER and you don't need to
know the password for the APP_USER that should own the jobs.
HTH
On Thu, Mar 9, 2023 at 2:54 PM Jeff Chirco <backseatdba_at_gmail.com> wrote:
> We have a lot of custom applications in our database all under locked
Chris
> 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-lReceived on Thu Mar 09 2023 - 22:34:04 CET