DB2 FOR LUW / DB2FORLUW / 980 - DB2

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 fro runstats is RR 
and therefore it will lock rows in SYSCOLUMNS that are not 
related to the table being updated.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Applications running alter, drop or create table willtimeout * 
* orwait until runstats completes giving the impression        * 
* thattheyare hung. They will be waiting for locks held by     * 
* theapplicationrunning runstats on another table.             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply Fix Pack                                               * 
****************************************************************

DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.8 Fix Pack 4 for AIX and Linux
 DB2 Version 9.8 Fix Pack 5 for AIX and Linux
 

Problem fixed in v98 FP3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.02.2010
10.01.2011
10.01.2011

9.8.FP3