DB2 FOR LUW / DB2FORLUW / A10 - DB2

When INSPECTing a damaged object DB2 may read bad pages into the 
bufferpool without detecting them. 
 
This happens with pages that belong to the same object and 
therefore look like a valid page. 
The actual corruption is the data pages being out of sync with 
the objects EMPs. 
 
A possible sequence of events that may result in the above 
corruption and instance PANIC is: 
- a not logged operation (NLI) against an object is 
aborted/rolled back 
- the object is in drop pending state after the NLI operation 
- INSPECT with option ERROR STATE ALL is executed against the 
object 
- error SQL1224N is hit and instance is brought down 
 
A possible stack may look like following: 
 
 ... 
 sqlb_panic 
 sqlbufix 
 dartCall_sqlbUnFixPage 
 dartUnfixPage 
 dartScanDAT 
 dartScanTable 
 dartScanTablespace 
 dartInspect 
 
This APAR will ensure DB2 detects the corruption upon fixing the 
page (sqlbfix) instead of successfully loading it into 
bufferpool and fail upon releasing/unfixing the page from 
bufferpool.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************

1) For objects with questionable states, do not use the FOR 
ERROR STATE ALL clause with INSPECT. 
2) For objects with questionable states, use db2dart to inspect 
them.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 1

keiner bekannt / siehe Local-Fix

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

13.06.2012
02.11.2012
02.11.2012