This checklist can help you troubleshoot problems that
occur while running tasks in the administrative task scheduler.
Procedure
- If your task does not execute as expected, the first thing
you should do is look for a execution status record in the ADMIN_TASK_STATUS
administrative view.
- If there is a record, examine the various values. In particular,
pay attention to the STATUS, INVOCATION, SQLCODE, SQLSTATE, SQLERRMC
and RC columns. The values often identify the root cause of the problem.
- If there is no execution status record in the view, the task
did not execute. There are a number of possible explanations for this:
- The administrative task scheduler is disabled. Tasks will not
execute if the administrative task scheduler is disabled. To enable
the scheduler, set the DB2_ATS_ENABLE registry
variable.
- The task was removed. Someone may have removed the task. Confirm
the task exists by querying the ADMIN_TASK_LIST administrative view.
- The scheduler is unaware of the task. The administrative task
scheduler looks for new and updated tasks by connecting to each active
database every five minutes. Until this period has elapsed, the scheduler
is unaware of your task. Wait at least five minutes.
- The database is inactive. The administrative task scheduler cannot
retrieve or execute tasks unless the database is active. Activate
the database.
- The transaction is uncommitted. The administrative task scheduler
ignores uncommitted tasks. Be sure to commit after adding, updating,
or removing a task.
- The schedule is invalid. The task's schedule might prevent the
task from running. For example, the task may have already reached
the maximum number of invocations. Review the task's schedule in the
ADMIN_TASK_LIST view and update the schedule if necessary.
-
If you cannot determine the cause of the problem by referring to the ADMIN_TASK_STATUS
administrative view, refer to the Db2® diagnostic log.
All critical errors are logged to the db2diag log file. Informational event
messages are also logged by the administrative task scheduler daemon during task execution. These
errors and messages are by identified by the "Administrative Task Scheduler" component.
What to do next
If
you follow the preceding steps and are still unable to determine the
cause of the problem, consider opening a problem management record
(PMR) with IBM Software
Support. Inform them that you have followed these instructions and
send them the diagnostic data that you collected.