My Oracle Support Banner

dbms_scheduler.stop_job Change the Session User To SYS (Doc ID 2275575.1)

Last updated on FEBRUARY 23, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Selecting user from dual returns SYS sometimes after using dbms_scheduler.stop_job.

However no SYS privileges can be executed.

 

Changes

After calling dbms_scheduler.stop_job('"'||c.job_owner||'"."'||c.job_name||'"');
The session user has changed (test case from SR) to SYS!!

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.