What is the difference between DBMS_JOB and DBMS_SCHEDULER ?
The DBMS_JOB package has been deprecated since 12cR2. Oracle 19c takes the demise of the DBMS_JOB package a step further by converting any DBMS_JOB jobs to DBMS_SCHEDULER jobs.
The DBMS_SCHEDULER package provides a collection of scheduling functions and procedures that are callable from any PL/SQL program.
Answer: As a review, the dbms_job.submit procedure accepts three parameters, the name of the job to submit, the start time for the job, and the interval to execute the job: dbms_job.submit( what=>'statspack_alert.sql;', next_date=>sysdate+1/24, -- start next hour.
If a job has been marked as broken with DBMS_JOB. BROKEN, or has been marked as broken by Oracle, Oracle will not attempt to execute the job until the broken status has been removed or the the job has been forced to execute.
From other forums:
Although dbms_job still exists in 10g and 11g, Oracle recommends the use of dbms_scheduler in releases 10g and up. No new features are being added to dbms_job and you will likely quickly run into its limitations.
dbms_scheduler is more robust and fully-featured than dbms_job and includes the following features that dbms_job does not have :
Features in releases after 10g Release 1 include :
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With