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 IC79271 Status: Geschlossen

IN DPF, XML QUERIES INCLUDING XMLTABLE EXPRESSIONS USING BIND-IN HOST
VARIABLES CAN RESULT IN BADPAGE ERROR DUE TO A BAD EXECUTI

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
This problem could happen when a correlation context (e.g., a 
bind-in host variable value, 
like the xmldoc in a query)  is being reversed TQed multiple 
times. In other words 
the problem is caused by a faulty execution plan which is 
sharing a data buffer 
across operators in different subsections 
 
Will the following errors in the db2diag.log file 
 
FUNCTION: DB2 UDB, Common Storage Layer, 
sqldcsl_getRecDataAndLength, probe:2414 
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, 20 bytes 
0x07000000784A0038 : 0000 0000 0000 0000 7FB4 0000 7FB3 0000 
................ 
0x07000000784A0048 : 0000 0014 .... 
CALLSTCK: 
[0] 0x0900000007339624 pdLog + 0xEC 
[1] 0x090000000A512810 
sqldcsl_fetchDirect__FP8sqeAgentP8SQLD_TCBP12SQLD_TCB_CSLP16SQLD 
CSL_FETCH_CB 
+ 0x25C 
[2] 0x090000000851E43C 
sqldcsl_fetchRow__FP8sqeAgentP8SQLD_TCBP12SQLD_TCB_CSLP16SQLDCSL 
_FETCH_CB 
+ 0x470 
[3] 0x0900000009A71D34 
xmls_FetchRecord__FP11XMLSTORE_CBR8XMLS_XIDPPcPUsT4UcP13XMLS_WA_ 
TOKENPP8SQLD_TCB 
+ 0xBB0 
[4] 0x09000000086CAE20 
fetchTempNode__12XmlrnNodeMgrFP11XMLSTORE_CBP17xmlDataDescriptor 
R8XMLS_XIDsRP9XmlrnNodePPcPUsP12XmlsNidStac 
kP13XMLS_WA_TOKENP8S + 0xEC 
[5] 0x0900000009FA2A80 
fetchNode__12XmlrnNodeMgrFP11XMLSTORE_CBP17xmlDataDescriptorR8XM 
LS_XIDR13XMLS_EXT_LXIDP12XmlsNidStackRP9Xml 
rnNodePUsP13XMLS_WA_ + 0x394 
[6] 0x090000000AD1A76C 
m_startNavOnContext__14XmlnvNavigatorFP17xmlDataDescriptorb + 
0x854 
[7] 0x090000000AD19E8C 
openNavigator__14XmlnvNavigatorFP17xmlDataDescriptorP8sqlrr_cb + 
0x940 
[8] 0x090000000A12E7DC sqlriXMLScan__FP8sqlrr_cb + 0x294 
[9] 0x090000000740F84C 
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x658
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This problem could happen when a correlation context (e.g.,  * 
* a bind-in host variable value, like the xmldoc in a query)   * 
* is being reversed TQed multiple times.                       * 
*                                                              * 
* In other words  the problem is caused by a faulty execution  * 
* plan which is sharing a data buffer across operators in      * 
* different subsections                                        * 
*                                                              * 
* The following errors are reported  in the db2diag.log file   * 
*                                                              * 
* FUNCTION: DB2 UDB, Common Storage                            * 
* Layer,sqldcsl_getRecDataAndLength, probe:2414                * 
* 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, 20 bytes                                  * 
* 0x07000000784A0038 : 0000 0000 0000 0000 7FB4 0000 7FB3 0000 * 
* ................                                             * 
* 0x07000000784A0048 : 0000 0014 ....                          * 
*                                                              * 
* CALLSTCK:                                                    * 
* [0] 0x0900000007339624 pdLog + 0xEC                          * 
* [1] 0x090000000A512810                                       * 
* sqldcsl_fetchDirect__FP8sqeAgentP8SQLD_TCBP                  * 
* [2] 0x090000000851E43C sqldcsl_fetchRow__FP8sqeAgent         * 
* [3] 0x0900000009A71D34 xmls_FetchRecord__FP11XMLSTORE_CB     * 
* [4] 0x09000000086CAE20                                       * 
* fetchTempNode__12XmlrnNodeMgrFP11XMLSTORE_CB                 * 
* [5] 0x0900000009FA2A80                                       * 
* fetchNode__12XmlrnNodeMgrFP11XMLSTORE_CB                     * 
* [6] 0x090000000AD1A76C m_startNavOnContext__14XmlnvNavigator * 
* [7] 0x090000000AD19E8C openNavigator__14XmlnvNavigatorF      * 
* [8] 0x090000000A12E7DC sqlriXMLScan__FP8sqlrr_cb + 0x294     * 
* [9] 0x090000000740F84C                                       * 
* sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x658          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 8                            * 
****************************************************************
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
First fixed in Version 9.7 Fix pack 8
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84524 IC89724 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.10.2011
31.12.2012
18.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6,
9.7.FP8
Problem behoben lt. FixList in der Version
9.7.0.6 FixList
9.7.0.7 FixList
9.7.0.8 FixList