home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC78823 Status: Closed

CRASH RECOVERY MAY FAIL WITH BAD PAGE ERROR DUE TO PROBLEM WITH EXTENT
MOVEMENT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Under a very rare condition after extent movement some but not 
all of the meta data about the location of a table might be 
flushed to disk.  This created an inconsistent view of the table 
on disk and if the database abnormally shutdown at this very 
same window then crash recovery will skip some of the processing 
because it sees the partial meta data on disk and thinks that it 
doesn't need to redo it.  This causes DB2 to fail to locate 
pages during crash recovery. 
 
This problem only applies to tablespace created in v97, and it 
only applies when the following command(s) has been run followed 
by a database abnormal shutdown: 
1. ALTER TABLESPACE ... LOWER HIGH WATER MARK 
2. ALTER TABLESPACE ... REDUCE MAX 
 
A possible symptom of the problem is bad page error from 
sqlb_verify_page: 
 
FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, 
probe:2 
MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad" 
          DIA8400C A bad page was encountered. 
DATA #1 : String, 64 bytes 
Error encountered trying to read a page - information follows : 
DATA #2 : String, 23 bytes 
Page verification error 
DATA #3 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes 
58304
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 fp6                                           * 
****************************************************************
Local Fix:
Contact service analyst.  A tablespace restore and rollforward 
might be necessary
available fix packs:
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

Solution
Fix is in v97 fp6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.09.2011
05.06.2012
05.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList