Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84265 Status: Closed

DB2 MAY PANIC DURING ATTEMPT TO UNFIX (SQLBUFIX) A PAGE FROM BUFFERPOOL

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
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.
available fix packs:
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

Solution
First fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
02.11.2012
02.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList