Remember, we didn't issue a COMMIT, so the job is not visible from another session connected to the same user. We can demonstrate this using the job created above. If a failure causes an exception, all the current work along with the jobs defined as part of it can be rolled back. One of the reasons people still use the DBMS_JOB package is it allows you to create jobs that are part of a bigger transaction. Notice the JOB_NAME of 'DBMS_JOB$_?' for the DBMS_SCHEDULER job that has been generated. We can see the job is listed in the USER_JOBS and USER_SCHEDULER_JOBS views. We create a job using the DBMS_JOB.SUBMIT procedure, but we are not going to issue a COMMIT statement.

Select job_name, job_action from user_scheduler_jobs We can see from the output below we don't have any jobs for this user. In Oracle 19c jobs created using the DBMS_JOB package are implemented as DBMS_SCHEDULER jobs, as demonstrated below. DBMS_JOB Jobs Converted to DBMS_SCHEDULER Jobs in Oracle Database 19c Onward.Security : The CREATE JOB Privilege is Required?.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_JOB package has been deprecated since 12cR2. Home » Articles » 19c » Here DBMS_JOB Jobs Converted to DBMS_SCHEDULER Jobs in Oracle Database 19c

Toad for oracle 19c