DBMS_SCHEDULER.CREATE_JOB Remove Implicit Commit

connor_mc_d-Oracle

As per the first sentence in my previous post

DBMS_JOB is no longer listed as deprecated

thus you can still use DBMS_JOB as per normal

Fernando Luna

Wouldn't calling DBMS_SCHEDULER procedures in an autonomous transaction take care of all of this?

David Kurtz

That already happens inside the DBMS_SCHEDULER procedures. The advantage of DBMS_JOB was that the update to the scheduler tables only commits with the rest of the transaction, otherwise, the request might start processes too soon.

Fernando Luna

I mention this because my recent experience has been the opposite (using Oracle 12c - perhaps this behavior doesn't happen with more recent versions of the RDBMS). I created a package procedure to call an Oracle Report and have it sent to DBMS_SCHEDULER. The existing code calls the report within a trigger.

Unless I specify PRAGMA AUTOMONOUS_TRANSACTION in my package call the trigger fails with ORA-04092.