Thanks!
A reader, December 02, 2016 - 1:05 pm UTC
Thanks for addressing this. It will be interesting to see what comes of it.
Anything new?
Marcus, February 22, 2018 - 7:40 am UTC
Have you found a solution for transactional jobs?
February 23, 2018 - 12:33 am UTC
Nope.
DBMS_JOB is still there in 18c.
Workaround
Racer I., February 23, 2018 - 10:55 am UTC
Hi,
Maybe something like this is possible : Add your own table where you store which jobs should run. Inserting the job-ID from the scheduler-start (I assume there is one) in your own transaction.
The job would only actually execute if its ID is in that table (and delete it at the end). It would need some grace period of retries waiting for the commit.
regards,
February 24, 2018 - 1:21 am UTC
It would need some grace period of retries waiting for the commit. Yeah, that's the kicker.
I'd strongly suggest people go to
https://community.oracle.com/community/database/database-ideas and log a request for DBMS_SCHEDULER to support a transactional extensions (perhaps for just plsql jobs)
deprecated
A reader, February 27, 2018 - 9:20 pm UTC
I wouldn't worry too much about deprecation.
Varchar datatype (as opposed to varchar2) has been deprecated as long as I've been using Oracle (more than 20 years), and it hasn't gone anywhere yet.
February 28, 2018 - 2:10 am UTC
Thats generally not a good game to play :-)