DBMS_SCHEDULER jobs running as "CREATOR" not OWNER (12.1.0.2)
From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Fri, 21 Jul 2017 08:09:02 -0500
Message-ID: <CAP79kiT4GvkZj+XfYibDenQrkwZiqteZ0cQHZ45D2dHqFQA+5A_at_mail.gmail.com>
DB: 12.1.0.2
Date: Fri, 21 Jul 2017 08:09:02 -0500
Message-ID: <CAP79kiT4GvkZj+XfYibDenQrkwZiqteZ0cQHZ45D2dHqFQA+5A_at_mail.gmail.com>
DB: 12.1.0.2
We have a release user for code releases, and this user has the manage scheduler priv and create any job (etc etc).
Recently, we ran some rollout scripts that created dbms_scheduler jobs.
The jobs show the correct owner (application ids) but the jobs are logged in as the release user from v$session.
I'm trying to figure out why (if this is by design or a bug) that a dbms_scheduler job would run as the creator and not the owner?
Trying to find documentation to this affect but I'm not finding it and checking to see if you guys have seen this behavior?
Chris
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Jul 21 2017 - 15:09:02 CEST