One thing, assuming you're on 19c, rather than locking the app accounts,
drop the passwords from them (i.e. set them to `no authentication`). Then
you can grant your DBAs proxy authentication to the app schemas and they
can create and schedule the jobs from within the schemas themselves. This
will eliminate all of the problems you listed. The active sessions will
show the owner schema. When a DBA account is dropped it will not drop the
jobs.
alter user app_schema no authentication;
alter user app_schema grant connect through dba_user;
connect dba_user[app_schema]@database_name...
Andy
On Thu, Mar 9, 2023 at 2:54 PM Jeff Chirco <backseatdba@xxxxxxxxx> 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
