home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC76182 Status: Closed

ASYNCHRONOUS INDEX CLEANUP EDU MAY NOT COMMIT FREQUENTLY ENOUGH

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In some situations, db2aicro, one of the system applications 
doing asynchronous index cleanup may not commit frequently 
enough such that it holds the oldest transaction causing the log 
space to fill up. Since system applications cannot be forced off 
by design, the database must be deactivated and/or the instance 
restarted to get out of this situation. 
 
Sample snapshot outputs: 
 
From the database snapshot, the application holding the oldest 
transaction is listed as follows i.e. 
 
Appl id holding the oldest transaction     = 7007 
... 
 
From the application snapshot for appl 7007, we can see that the 
"Is this a System Application" field equals "YES". Note that the 
app name is: db2aicro 
 
Application handle                         = 7007 
Application status                         = UOW Executing 
Status change time                         = 04/18/2011 
02:47:36.562136 
Application code page                      = 1208 
Application country/region code            = 1 
DUOW correlation token                     = 
*LOCAL.DB2.110418074736 
Application name                           = db2aicro 
Application ID                             = 
*LOCAL.DB2.110418074736 
Sequence number                            = 02492 
TP Monitor client user ID                  = 
TP Monitor client workstation name         = 
TP Monitor client application name         = 
TP Monitor client accounting string        = 
Is this a System Application               = YES
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See the description above.                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP5 or higher.                            * 
****************************************************************
Local Fix:
Since system applications cannot be forced off by design, the 
database must be deactivated and/or the instance restarted to 
get out of this situation.
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
Problem first fixed in DB2 version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2011
06.02.2012
06.02.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList