DB2 FOR LUW / DB2FORLUW / 970 - DB2

Catalog cache locks with badly formed lock names may be stored 
in various catalog cache entries.  This can result in multiple 
applications requesting cache locks with the exact same bad lock 
name, leading to serialization (ending in possible lock 
waits/lock timeouts) or even deadlocks. 
 
You can identify this problem in your environment by collecting 
lock snapshots, or using event monitors to show the lock names 
involved in deadlocks or lock timeouts. If the lock name appears 
as follows: 
 
0x00000000000000000000000043 
 
You may be experiencing this problem.  The '43'  at the end of 
this lock name is critical to identifying this APAR.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA through to Fix Pack 1 servers on      * 
* Linux, Unix, and Windows environments                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Bad lock names may be stored in the catalog cache entries    * 
* for the optimization profile cache, and the systables cache. * 
*  The systables cache can only have this symptom if views are * 
* getting regenerated from the non-catalog node.               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 9.7 Fix Pack 2.                            * 
****************************************************************

You can avoid some of these issues by ensuring invalid views are 
revalidated after maintenance is performed on base tables. 
Perform the revalidation from the catalog node to avoid this 
issue.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem is first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

02.02.2010
08.04.2010
08.04.2010

9.7.FP2