Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91954 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
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.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.04.2013
02.10.2013
02.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList