My Oracle Support Banner

After upgrading to 19c, the NEXT_RUN_DATE of a job changed unexpectedly. (Doc ID 3026234.1)

Last updated on MAY 31, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

 After migrating to 11g to 19c via datapump, scheduler start_date was showing incorrect time.

 

 
11g - job information

BEGIN SYS.DBMS_JOB.SUBMIT(
     JOB=> 41,
     LUSER=> '<username>',
     PUSER=> '<username>',
     CUSER=> '<username>',
     NEXT_DATE=> TO_DATE('2024-05-09 00:00:00', 'YYYY-MM-DD:HH24:MI:SS'), <- For 11g, next_date was set to occur on 5/9/24 at 00:00
     INTERVAL=> 'TRUNC(SYSDATE+1)',

................

 

after import to 19c, we can see that next_run_date has changed to 09:00.

 
OWNER      JOB_NAME      START_DATE                         REPEAT_INTERVAL     NEXT_RUN_DATE
---------- -----------   ---------------------------------  ---------------    -----------------------------------
TESTADM DBMS_JOB$_41    14-MAY-24 09.00.00.000000 AM +09:00  TRUNC(SYSDATE+1   14-MAY-24 09.00.00.000000 AM +09:00

 

Changes

Upgrade from 11g to 19c via datapump.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.