DB2 - Problembeschreibung
Problem IC95280 | Status: Geschlossen |
UNDER RARE CONDITIONS, AUTOMATIC STATISTICS COLLECTION CAN LEAD TO AN ACTIVE LOG FULL CONDITION. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - 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: * * software * **************************************************************** * PROBLEM DESCRIPTION: * * AUTOMATIC STATISTICS COLLECTION CAN LEAD * * TO AN ACTIVE LOG FULL CONDITION * **************************************************************** * RECOMMENDATION: * * Update to 10.5.0.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.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem Fixed In 10.5.0.3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.08.2013 16.06.2014 16.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.3 | |
10.5.0.3 |