DB2 FOR LUW / DB2FORLUW / A10 - DB2

The following db2diag.log error may occur when accessing XML 
column data in stored procedure variables. 
 
FUNCTION: DB2 UDB, Common Storage Layer, 
sqldcsl_getRecDataAndLength, probe:2461 
MESSAGE : ZRC=0x87A80001=-2019033087=SQLDCSL_BADPAGE "Bad Data 
Page" 
          DIA8500C A data file error has occurred, record id is 
"". 
DATA #1 : signed integer, 8 bytes 
0 
DATA #2 : Hexdump, 30 bytes 
0x07700000358D8038 : 0000 0000 0000 0000 172A 0000 1733 0005 
.........*...3.. 
0x07700000358D8048 : 0002 0014 1734 4B74 FFFF FFFF FFFF 
.....4Kt...... 
CALLSTCK: 
  [0] pdLog + 0xC0 
  [1] xmls_FetchRecord 
  [2] fetchTempNode 
  [3] initWalker 
  [4] initWalker 
  [5] serialize 
  [6] sqlriMaterializeXml 
  [7] sqlribnoLobCbDrda 
  [8] sqlribno 
 
The problem depends on the content of an uninitialized memory 
area and is therefore not easily reproducable. 
The error does not indicate any database corruption. 
The problem can be avoided when not directly using the content 
of variables for both the input value for a cursor and the 
target for the select column. 
 
e.g. avoid using : 
 
DECLARE var1 XML; 
DECLARE c1 CURSOR FOR stmt; 
.. 
OPEN c1 USING var1 ... 
FETCH c1 INTO var1 ... 
 
but use : 
 
DECLARE var1 XML; 
DECLARE var2 XML; 
DECLARE c1 CURSOR FOR stmt; 
.. 
OPEN c1 USING var1 ... 
FETCH c1 INTO var2 ...

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 server to V10 Fix Pack 1                     * 
****************************************************************

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
 

This problem was first fixed in DB2 V10 Fix Pack 1

keiner bekannt / siehe Local-Fix

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

14.06.2012
06.11.2012
06.11.2012