SYS_CONTEXT('USERENV', 'SESSIONID') Recorded at the Start of a DBMS_SCHEDULER Job is Different at the Completion of the Job
(Doc ID 2476943.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Database - Standard Edition - Version 188.8.131.52 and later
Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
When using dbms_scheduler to run a job the SESSION_ID returned from SYS_CONTEXT changes from the start of the job to the completion of the job
The following simple test case demonstrates the issue
The resulting output demonstrates that the SESSIONID changes after upgrading to 220.127.116.11
start:4294967295 <-----------SESSIONID value returned at create job
session end:4294967295 <---------SESSIONID remains the same at completion of job
session start:20112438 <-----------SESSIONID value returned at create job
session end:20113608 <---------SESSIONID remains the same at completion of job
session start:4507723 <---------SESSIONID remains the same at completion of job
session end:4507745 <---------SESSIONID changes at completion of job
Upgrade to 18.104.22.168 or later
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