DB2 FOR LUW / DB2FORLUW / 950 - DB2

In heavy workload situations, a rare timing hole may cause index 
recreation to fail with a message in db2diag.log similar to the 
following: 
 
2010-10-21-01.46.11.845112+480 I2267924A490       LEVEL: Severe 
PID     : 574054               TID  : 18607       PROC : db2sysc 
34 
INSTANCE: db2inst1             NODE : 034         DB   : SAMPLE 
APPHDL  : 0-1574               APPID: 
10.238.100.51.25797.10102017410 
AUTHID  : ETL20 
EDUID   : 18607                EDUNAME: db2agntp (SAMPLE) 34 
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateIndexObject, 
probe:30 
RETCODE : ZRC=0x8404007E=-2080112514=SQLD_IXNOEX "INDEX DOES NOT 
EXIST" 
 
In such situations, the database may be marked bad.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An issue with lock escalation during index recreate could    * 
* cause DB2 to trap and erroneously mark the database as bad.  * 
* In such cases, the data in the database is actually fine.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 8.                       * 
****************************************************************

DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 9.5 Fix Pack 8.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC72889 IC72890 
Nachfolger : 

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

24.11.2010
05.07.2011
05.07.2011

9.5.FP8