My Oracle Support Banner

Job Scheduler-Next Run Date not getting updated with correct date and time (Doc ID 2909527.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Oracle Financial Services Lending and Leasing Cloud Service - Version 14.10.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Job Scheduler-Next Run Date not getting updated with correct date and time

Scenario - If there is failure in any of the EOD jobs and resumed it a later, next run date time for all the pending jobs is updated with the date and time  of resumed job.
 
EXPECTED BEHAVIOR
-----------------------
Next Run Date and time should be according to the job completion and job set up. 

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start the 1st job set (JBS-1) in the EOD as per the schedule. Make sure scheduled service and job service status is running.
2. After the completion of JBS-1, the next job set JBS-2 will trigger as defined in the sequence and the time mentioned in the job scheduler.
3. Update the data so that  second Job Set JB2 is failed
4. Do not re-submit the failed job (JBS-2) until the system date is crossing the "JSC_START_OF_BUSINESS_TIME" set up in the parameter. E.g. If this parameter value is 06:00, resubmit the JBS-02 at 06:30.
5. Resubmit JBS-2, Check next run date time for all the remaining job sets. 
6. Since the system set the job run time to the value greater than JSC_START_OF_BUSINESS_TIME, GL Date flip is happening even though the critical job sets haven't completed in the EOD Batch.


Changes

 

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


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