Sessionid for jobs started by DBMS_SCHEDULER is always equal 0
28655Aug 27 2007 — edited Oct 5 2007Hello everyone,
I would like to use DBMS_SCHEDULER to run night batch jobs. Currently we use Linux cron scheduler. When I start exactly the same batch job from DBMS_SCHEDULER, it always gets assigned sessionid = 0. We have number of places in the backend of our application where we assume that each session has unique value for USERENV('SESSIONID').
Does anyone know work around for the problem? Your help is greatly appreciated.
Thank you very much,
Boris