scheduler job_creator is DBA user account
From: Jeff Chirco <backseatdba_at_gmail.com>
Date: Thu, 9 Mar 2023 12:53:08 -0800
Message-ID: <CAKsxbLooz4p=p=cF6RH+x2PuwoFQu3mS4GXu6epuTSdmWbUXDw_at_mail.gmail.com>
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.
Date: Thu, 9 Mar 2023 12:53:08 -0800
Message-ID: <CAKsxbLooz4p=p=cF6RH+x2PuwoFQu3mS4GXu6epuTSdmWbUXDw_at_mail.gmail.com>
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-lReceived on Thu Mar 09 2023 - 21:53:08 CET