home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80113 Status: Geschlossen

BAD DATA PAGE ERROR ACCESSING XML COLUMN DATA WITHIN STORED PROCEDURE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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 ...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using XML datatype                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V9.7 Fix Pack 6               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
This problem has first been fixed in V9.7 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84400 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.12.2011
18.06.2012
18.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList