|
Problem IC78518
|
Status: Closed |
DEACTIVATING DATABASE LEADS TO REMOVAL OF ALL ADMIN TASK SCHEDULER TASKS BELONGING TO ANY ACTIVE DATABASES |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When there is more than one active databases (e.g. there are 3
databases SAMPLE1, SAMPLE2 and SAMPLE3 in the DB2 instance),
deactivating any of the databases (e.g. SAMPLE2) leads to
removal of all the tasks including tasks belonging to SAMPLE1
and SAMPLE3 in the tasklist maintained by Administrative Task
Scehduler.
Tasks will be added back to the pending tasklist only when task
is updated or the next time particular database is activated
when there are no other active connections to that database. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See ERROR DESCRIPTION. *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 v9.7 Fixpack 6 or newer *
**************************************************************** |
| Local Fix: |
Do not deactivate any database. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 6. At minimum this fix
should be
applied to the server. |
| Workaround |
See LOCAL FIX. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.09.2011
05.06.2012
18.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5,
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
