DB2 - Problembeschreibung
Problem IT09468 | Status: Geschlossen |
ATS CAN MISS SOME TASKS IF TASK IS NOT COMMITTED BEFORE SCHEDULER WAKES UP | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5, Fix pack 7 * **************************************************************** | |
Local-Fix: | |
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. | |
Lösung | |
First fixed in DB2 Version 10.5, Fix pack 7 | |
Workaround | |
see Local Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.06.2015 29.01.2016 29.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |