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 IC91562 Status: Closed

UNDER RARE CONDITIONS, AUTOMATIC STATISTICS COLLECTION CAN LEAD TO AN
ACTIVE LOG FULL CONDITION.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When auto_runstats and auto_stmst_stats are both enabled, at any 
given time, two automatic runstats might be running against 
different tables.  The runstats operation requires very few 
locks.  But, when it requests a lock, if LOCKLIST has been been 
exhausted at that point in time, it will experience lock 
escalation.  Under the rare conditions where auto_stmt_stats is 
performing an automatic runstats, and auto_runstats experiences 
lock escalation while performing another automatic runstats, the 
latter might have to wait for the former to complete.  If the 
auto_stmt_stats runstats is against a large table with multiple 
indexes, it might take some time to complete, and the waiting 
auto_runstats runstats might have to wait for a significant 
amount of time.  In this situation, active log full can be 
reached.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.7 on LUW users.                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack9 or higher.                     * 
****************************************************************
Local Fix:
To eliminate a long or indefinite wait, configure the 
LOCKTIMEOUT database parameter to the maximum time that an 
application should wait for a lock.
available fix packs:
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
Fixed in DB2 V9.7 Fix Pack 9.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91954 IC95280 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.04.2013
25.08.2014
25.08.2014
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList