DB2 FOR LUW / DB2FORLUW / A50 - DB2

The error might occur when the following criteria are met: 
 
1) The table is a multidimensional clustering (MDC) table. 
 
2) The table uses extended row size. New in DB2 version 10.5, 
extended row size support allows you to create a table where its 
row length can exceed the maximum record length for the page 
size of the table space. 
 
3) A rollout delete is performed on the table. The conditions 
that need to be met for a delete to be 
classified as a rollout delete are: 
   - The DELETE statement is a searched DELETE, not a positioned 
DELETE (the statement does not use the WHERE CURRENT OF clause). 
   - There is no WHERE clause (all rows are to be deleted), or 
the only conditions in the WHERE clause apply to dimensions. 
   - The table is not defined with the DATA CAPTURE CHANGES 
clause. 
   - The table is not the parent in a referential integrity 
relationship. 
   - The table does not have ON DELETE triggers defined. 
   - The table is not used in any MQTs that are refreshed 
immediately. 
   - A cascaded delete operation might qualify for rollout if 
its foreign key is a subset of the table's dimension columns. 
   - The DELETE statement cannot appear in a SELECT statement 
executing against the temporary table that identifies the set of 
affected rows prior to a triggering SQL operation (specified by 
the OLD TABLE AS clause on the CREATE TRIGGER statement). 
 
4) The rollout delete hits a non-severe error while executing 
the DB2 internal function named sqldRolloutRecordPass1. 
Examples of non-severe errors include interrupts and 
out-of-memory errors. 
 
If these conditions are met, then the problem might be hit.  The 
symptom is that the db2diag.log will contain a SQLD_BADPAGE 
error from the sqldRolloutRecordPass1 function (despite the fact 
that no bad-page was encountered) and the database will be 
forced to shutdown.  Here is an example of such a db2diag.log 
entry. 
 
2015-02-05-09.30.56.054858-300 I54296E574   LEVEL: Severe 
PID     : 10555       TID : 46913076324672  PROC : db2sysc 
INSTANCE: db2usr1     NODE : 000            DB   : MYDB 
APPHDL  : 0-36        APPID: *LOCAL.db2usr1.150205143111 
AUTHID  : DB2USR1     HOSTNAME: myHost 
EDUID   : 18          EDUNAME: db2agent (MYDB) 
FUNCTION: DB2 UDB, data management, sqldRolloutRecordPass1, 
probe:1207 
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data 
Page" 
DIA8500C A data file error has occurred, record id is "".

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.7.                             * 
****************************************************************

If the error is encountered, execute the RESTART DATABASE 
command to execute crash recovery and resume database 
processing.  No permanent damage should have occurred. 
 
To avoid hitting the problem do not create multidimensional 
clustering (MDC) tables that use the extended row size feature 
or, if such a table was already created, disable the rollout 
delete optimization by executing the following command and then 
recycling the instance: 
db2set DB2_MDC_ROLLOUT=OFF

The problem is first fixed in DB2 version 10.5.0.7.

keiner bekannt / siehe Local-Fix

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

05.02.2015
20.01.2016
20.01.2016