DB2 FOR LUW / DB2FORLUW / 970 - DB2

In very rare case, db2 may crash in following scenario: 
 
1. Replaying logs on standby 
2. During crash recovery on primary or standby 
3. Rolling forward the logs after restore is done 
 
This APAR can be hit only when the following condition 1 and one 
of the conditions in 2(a or b or c) are met: 
 
1. Index compression is on. User can identify compressed index 
by querying ADMIN_GET_INDEX_COMPRESS_INFO table function for 
column index_compressed . 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?t 
opic=/com.ibm.db2.luw.sql.rtn.doc/doc/r0054897.html 
2. 
a) Reorg on compressed index is issued with Cleanup only all 
option. 
b) A delete on an exclusively locked table is done, and index is 
having a non-zero MINPCTUSED defined. 
c) ALTER TABLE...DETACH PARTITION operation on a partitioned 
index of a partitioned table 
 
 
To confirm the APAR, formatted LOG file has MERGEOPT_LEAF_DP for 
a compressed index with 1 suffix and 1 prefix in the right page. 
 
db2diag.log shows : 
 
 
2011-03-16-07.01.40.103486+000 I2183241A459       LEVEL: Warning 
 
PID     : 12345678             TID  : 1310       PROC : db2sysc 
0 
INSTANCE: db2inst1           NODE : 000         DB   : HADR 
 
APPHDL  : 0-1                  APPID: *LOCAL.DB2.1315190544 
 
EDUID   : 1310                EDUNAME: db2redow (HADR) 0 
 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:600 
 
DATA #1 : String, 12 bytes 
 
 sqlirorg__F 
 
DATA #2 : String, 4 bytes 
 
sqli 
 
 
Trap file shows the stacktrace as : 
 
StackTrace> 
 
-------Frame------ ------Function + Offset------ 
 
0x000000000000F424 ?unknown + 0x0 
 
0x090000000E9B550C 
 
sqlirorg__FP7SQLI_CBP14SQLI_PAGE_DESCPcP9SQLI_SLOTUlT5 + 0x5C 
 
0x0900000010EFE55C sqliRedo__FP8sqeAgentPcP9SQLP_LSN8UlT4 + 
0x494C 
0x090000000F72424C 
 
sqldmrdo__FP8sqeAgentP9SQLP_LSN8PcUlN34P8SQLP_TIDP15SQLD_RECOV_I 
NFO 
+ 
0x5D0 
 
0x090000000F51B474 
 
sqlpRecDbRedo__FP8sqeAgentP8SQLP_ACBP9SQLP_DBCBP10SQLP_FRAPPP11S 
QLP_TENT 
 
RYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x6BC 
 
0x090000000E614054 
sqlpPRecProcLog__FP8sqeAgentP8SQLP_ACBP9SQLP_DBCB + 
0x480 
 
0x090000000E60B18C sqlpParallelRecovery__FP8sqeAgentP5sqlca + 
0xC30 
0x090000000F507504 sqleSubCoordProcessRequest__FP8sqeAgent + 
0x208 
0x090000000E2BB368 RunEDU__8sqeAgentFv + 0x3C0 
 
0x09000000120F5D48 EDUDriver__9sqzEDUObjFv + 0xDC 
 
0x0900000012100898 sqloEDUEntry + 0x260 
 
</StackTrace>

**************************************************************** 
* USERS AFFECTED:                                              * 
* All with index compression                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to IBM Db2 v9.7 Fix Pack 4                           * 
****************************************************************

Mark the index invalid by db2dart /MI option for the indexes 
reorg was issued for.

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 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First Fixed in v9.7 Fix pack 4

keiner bekannt / siehe Local-Fix

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

21.03.2011
20.06.2011
23.07.2012

9.7.FP4