DB2 FOR LUW / DB2FORLUW / 970 - DB2

If a Load into a table that resides in an SMS tablespace fails 
and the table is left in Load Pending state (ie. a Load 
Terminate is not yet executed), and a Backup is executed, then 
the backup may fail with a SQLB_BADP error. 
 
An entry similiar to the following can be seen in the 
db2diag.log. 
 
2010-03-04-15.13.13.612849-300 I27099E3778         LEVEL: Severe 
PID     : 20028                TID  : 47983534008640PROC : 
db2sysc 
INSTANCE: xxxxxxxx             NODE : 000          DB   : 
XXXXXXXX 
APPHDL  : 0-18                 APPID: 
*LOCAL.xxxxxxxx.100304201315 
AUTHID  : xxxxxxxx 
EDUID   : 66                   EDUNAME: db2bm.19.3 (XXXXXXXX) 
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 
1000 
DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 88 bytes 
    Obj: {pool:4;obj:2;type:0} Parent={4;2} 
 
Note that the DATA#3 value in this db2diag.log entry (1000 in 
this example) represents the page number,  and this value 
modulus 500 will always be 0 when this particular APAR is 
encountered.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users with table(s) reside in SMS tablespace.                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW version 9.7, Fixpack 3.                   * 
****************************************************************

To resolve the issue, follow the steps below - 
 
1. invoke a Load Query to confirm the table is in Load_Pending 
   state, 
2. perform a Load TERMINATE to bring the table out of 
   Load_Pending state, 
3. invoke the Backup. 
 
Alternatively, the problem does not occur if the table resides 
in 
a DMS or AUTOMATIC STORAGE tablespace.

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 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 DB2 Version 9.7, Fixpack 3.

n/a

forerunner  : APAR is sysrouted TO one or more of the following: IC69134 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

05.03.2010
08.11.2010
06.07.2011

9.7.FP3