|
Problem IT32672
|
Status: Closed |
PERIODIC TASKS THAT RUN THROUGH DB2ACD ARE NOT EXECUTED AFTER HADR FAIL OVER
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Periodic background work that is run through the db2acd process
including automatic backups, automatic reorgs, automatic
runstats, and tasks scheduled by the automatic task scheduler
(ATS) may not execute correctly after an hadr takeover.
The task status and completion for ATS tasks can be verified
using the following queries:
db2 "select * from SYSTOOLS.ADMIN_TASK_LIST"
db2 "select * from SYSTOOLS.ADMIN_TASK_STATUS"
Automatic reorgs / automatic runstats / automatic backup
execution can be validated by checking for entries in the
db2diag.log. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users on DB2 v11.1 FP5 and earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v111 m4 FP6 *
**************************************************************** |
| Local Fix: |
As a workaround, you may kill db2acd process, after which,
periodic tasks that run through db2acd will continue execution:
kill -6/-9
The process id of db2acd process can be obtained from db2pd
-edus output:
db2pd -edus |grep db2acd |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All Users on DB2 v11.1 FP5 and earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v111 m4 FP6 *
**************************************************************** |
| Comment |
First Fixed in DB2 v111 m4 FP6 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.04.2020
26.04.2021
26.04.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
