DB2 FOR LUW / DB2FORLUW / A50 - DB2

The administrative task scheduler (ATS) can miss some tasks in 
the rare condition where the last schedule time occurred between 
the job was submitted (update_time) and the time it was 
committed. 
 
For Example: 
 
  - User calls DBMS_JOB.SUBMIT(task)  UPDATE_TIME is set in the 
TASKLIST table. 
  - Scheduler scans TASKLIST but ONLY for committed rows, so the 
task is not selected. 
  - User commits the call to DBMS_JOB.SUBMIT(task). 
 
The reason is that on the next run of the scheduler only tasks 
with UPDATE_TIME > LAST_SCHEDULE_TIME will be selected and in 
this case the specific 'task' will NEVER be selected unless the 
DB2 engine is recycled/restarted.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5, Fix pack 7                      * 
****************************************************************

The DBMS_JOB.RUN(task) command can be used to execute a task 
that was missed.  This also needs to be committed as well before 
the scheduler wakes up.

First fixed in DB2 Version 10.5, Fix pack 7

see Local Fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.06.2015
29.01.2016
29.01.2016