DB2 - Problembeschreibung
Problem IC66059 | Status: Geschlossen |
RUNSTATS GENERATES EXCESSIVE LOCKING IN SYSCOLUMNS AND LOCK TIMEOUTS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Running runstats at the time other DDL modifying statements are running will likely encounter lock timeouts or deadlocks. The investigation revealed that the lock contention are on object that are not related to the RUNSTATS. Applications running alter, drop or create table will timeout or wait until runstats completes giving the impression that they are hung. They will be waiting for locks held by the application running runstats on another table. The isolation level used to update columns for runstats is Repeatable Read (RR) and therefore it will lock rows in SYSCOLUMNS that are not related to the table being updated. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Runstats generates excessive locking. Application * * willlocktimeout while trying DDL commands on objects that * * arenotrelated to the runstats command * **************************************************************** * RECOMMENDATION: * * Migrate to v95fp6 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Fixed in v95fp6 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Kommentar | |
FIN | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66177 IC66311 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.02.2010 22.06.2010 20.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |