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

DB2 INSTANCE CRASH RESULTING IN BADPAGE ERROR WHEN RUNNING XML QUERIES IN
A DPF ENVIRONMENT.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A DB2 instance crash can occur with BADPAGE error while 
executing XML queries in DPF environment under the following 
conditions: 
 
1. Internally we are running into a special case of distributed 
DSS where all work is done on the coordinator partition. 
 
2. We are using Table Queues to send/receive XML data between 
database agents. 
 
 
 
Example plan: 
 
 
Plan Graph: 
 
                Rows 
              Operator 
                (ID) 
                Cost 
 
              160000 
              RETURN 
               ( 1) 
              83268.5 
                | 
              160000 
                BTQ 
               ( 2) 
              83268.5 
                | 
              160000 
               NLJN 
               ( 3) 
              70482.9 
             /       \ 
      2000              80 
       DTQ             SCAN 
      ( 4)             ( 8) 
     58021.2          4799.81 
       |                | 
      2000              80 
      NLJN             TEMP 
      ( 5)             ( 9) 
     57840.2          4794.8 
    /       \          | 
  2000      1          80 
  SCAN    XSCAN       NLJN 
  ( 6)    ( 7)        (10) 
 160.227  57.68      4792.43 
   |                /       \ 
  2000             80       1 
  n/a             SCAN    XSCAN 
 Table:           (11)    (12) 
 <17,4>          178.027  57.68 
                   | 
                  2000 
                  n/a 
                 Table: 
                 <17,5> 
 
 
 
Stack should show the special DSS case where we have sqlritqa 
back to back in the trace: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000004AF6BC pthread_kill + 0x88 
0x090000000947ED3C sqloDumpEDU + 0x54 
0x0900000009D12C08 MarkDBBad__16sqeLocalDatabaseFi + 0x274 
0x09000000094824A4 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0x814 
0x090000000B8B0DCC 
sqldcsl_dumpBadPage__FP8sqeAgentP8SQLD_TCBP16SQLB_OBJECT_DESCP11 
SQLB_FIX_CBUiP16SQLDCSL_PAGESLOTiT7CUle 
+ 0x90 
0x090000000A9ED22C 
sqldcsl_1RowDelete__FP8sqeAgentP8SQLD_TCBP12SQLD_TCB_CSL8SQLZ_RI 
D 
+ 0x6C4 
0x090000000A9EC9A8 
xmlsDelete1TempRecNoWAReset__FP11XMLSTORE_CB8SQLZ_RIDP8SQLD_TCB 
+ 0x38 
0x090000000A9EE728 
deleteXTemps__19SqlriXmlTempManagerFP8sqlrr_cb + 0x5E4 
0x090000000BEA449C 
deregisterSectObj__19SqlriXmlTempManagerFPUcP8sqlrr_cb + 0x17C 
0x090000000AD6C6F8 sqlritqa__FP8sqlrr_cb + 0x17C 
0x090000000AD6CFB8 sqlritqa__FP8sqlrr_cb + 0x394 
0x0900000009161FE8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x590 
0x0900000009380CBC 
sqlrr_process_fetch_request__FP14db2UCinterface + 0x1C8 
0x0900000009B3367C 
sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0xFC 
0x09000000090F48C8 
sqljs_ddm_opnqry__FP14db2UCinterfaceP13sqljDDMObject + 0xCDC 
0x09000000090FC43C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
+ 0x84 
0x09000000090FC22C 
.sqljsParse.fdpr.clone.67__FP13sqljsDrdaAsCbP14db2UCinterface + 
0x334 
0x09000000090FA068 @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x448 
0x090000000901C6F4 
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
0x090000000901C53C 
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x2AC 
0x090000000901BBCC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x100 
0x09000000092CC414 RunEDU__8sqeAgentFv + 0x70 
0x09000000092D44C4 EDUDriver__9sqzEDUObjFv + 0x100 
0x09000000092C55AC sqloEDUEntry + 0x278 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW ALL                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* View APAR Information Tab => Error Description.              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 FP3                                           * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Fix was delivered to v97 FP3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.05.2010
07.10.2010
07.10.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList