Bug 13860788: Deferred Jobs Are Not Working. They Start Immediately. (Doc ID 2100996.1)

Last updated on OCTOBER 26, 2016

Applies to:

Oracle Life Sciences Data Hub - Version 2.2.1 and later
Information in this document applies to any platform.

Symptoms

The option of deferring a Job is not working. The User's Guide indicates Deferred should schedule the job, instead of executing immediately:
 

Oracle® Life Sciences Data Hub User's Guide Release 2.2 =>   5 Generating Reports and Running Other Jobs =>  Setting Submission Details
Submission Type From the drop-down list, select the timing of the submission:

 Deferred. The system displays additional screens to allow you to schedule a single execution at a later time. Enter the date and time you want to execute the job in the fields that appear at the bottom of the section.


Instead of starting the Job at the entered time, the system is starting the Job immediately. It reproduces consistently.

Steps to Reproduce
---------------------------
1. Started a Loadset job, submission type "Deferred".
2. Enter a start time in the future, click on submit.
3. Check the job and it is started immediately.


EXPECTED BEHAVIOR
---------------------------------
Expected that the job with the Submission Type set to 'Deferred' should be executed in the future at the time when it was scheduled.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms