Well, that's just bizarre and incredibly sad :/
Chris
On Fri, Jul 21, 2017 at 8:15 AM, Rich J <rjoralist3@xxxxxxxxxxxxxxxxxxxxx>
wrote:
On 2017/07/21 08:09, Chris Taylor wrote:
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
Hey Chris,
This (unfortunately) isn't new to 12.1. Check out this thread:
https://www.freelists.org/post/oracle-l/How-to-best-
schedule-jobs-in-another-schema
Good luck!
Rich
