Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

DBMS_JOB Issues In 19c (Doc ID 2731533.1)

In this Document

Purpose
Scope
Details
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 19.0.0.0 to 19.9.0.0.0 [Release 19]

Information in this document applies to any platform.

PURPOSE

This Primary Note is intended to provide an index and references to the bugs created for the DBMS_JOB issues in 19c
version .

SCOPE

This note helps to find the bugs created for the DBMS_JOB issues in 19c version and their details .

Even though Oracle continues to support the DBMS_JOB package, internal working has changed from 19c. Starting
with Oracle Database 19c, jobs which were created and managed through DBMS_JOB package in the previous
database versions will be re-created using Oracle Scheduler architecture. Also for each new job in DBMS_JOB, a
corresponding entry will be created with DBMS_SCHEDULER. But there are some issues reported with the DBMS_JOBs .
So this document helps to find the bugs and their details .

DETAILS

1. Oracle recommends to move all your DBMS_JOBS to DBMS_SCHEDULER . And create a new jobs using the
DBMS_SCHEDULER only as the DBMS_JOBS are kept for backward compatibility and going forward it will be
decommissioned .

https://docs.oracle.com/cd/B19306_01/server.102/b14231/jobtosched.htm

IF: An Example to Convert from DBMS_JOB Jobs to DBMS_SCHEDULER Jobs (Doc ID 2117140.1)

2. Below are the DBMS_JOBs issue in 19c reported .

i. Bug 30882524 - ISSUE WITH DBMS_JOB WHEN USED FIXED_DATE IN 19C VERSION .

This is under Development Working.

ii. BUG 30919609 - TOTAL_TIME VALUE REMAINS 0 TO DBA_JOBS IN ORACLE 19C.

This is currently under Development working

iii. BUG 31658679 - JOBS LAUNCHED WITH DBMS_JOB.RUN AREN'T VISIBLE IN DBA_JOBS_RUNNING .
This is currently under Development working

iv. BUG 31702289 - DBMS_JOB.SUBMIT NOT CREATING NEW JOB IN 19C IF THE INTERVAL PARAMETER IS NULL .

This is closed as "Couldn't able to Reproduce" The workaround is to move the DBMS_JOBs to DBMS_SCHEDULER

v. BUG 31824934 - DBMS_JOB SYS_CONTEXT BG_JOB_ID NOT PASSED CORRECTLY SINCE 19C UPGRADE.

This bug is fixed . Refer Doc ID 31824934.8 for Affected version and fixed version. You can backport the patch if its not
available.

working as expected but not in 19c versions.

The last_date and next_date column in dba_jobs table is showing current_date

instead of sysdate /the date hard coded using the fixed_date parameter. Where

in previous releases 12.2 and 11.2.0.4 it is using sysdate which is set by

using the fixed_date

Bug is with the development team .

Didn't find what you are looking for?