home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC95386 Status: Closed

In a DPF environment, an access plan with a listener TQ operator may
encouter a NULL pointer and cause DB2 to crash.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
A DB2 crash occurs in an access plan with a listener TQ operator 
if the following conditions are true: 
 
1) In a DPF environment 
2) A query is run that features a correlated subquery. 
3) The query compiler chose an access plan for this query that 
contains a listener TQ to flow the correlated values. 
4) There is an operation against the correlated column in the 
subquery that happens as a pushdown operation.  This problem was 
discovered for a scenario where an aggregation (for example, 
sum, min, max...) was being done against the correlated column. 
 
This crash produces similar errors in the db2diag.log: 
2013-04-24-16.36.52.495582-240 I42353678E620         LEVEL: 
Severe 
PID     : 16424                TID : 140291218597632 PROC : 
db2sysc 0 
INSTANCE: userid               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-152                APPID: *N0.userid.130424203620 
AUTHID  : USERID               HOSTNAME: lab01 
EDUID   : 1373                 EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:250 
RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR 
          "Severe programming error" 
          DIA8516C A severe internal processing error has 
occurred. 
 
2013-04-24-16.36.52.684856-240 E42504930E1608        LEVEL: 
Severe 
PID     : 16424                TID : 140291218597632 PROC : 
db2sysc 0 
INSTANCE: userid               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-152                APPID: *N0.userid.130424203620 
AUTHID  : USERID               HOSTNAME: lab01 
EDUID   : 1373                 EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The DB2 database manager cannot recover from 
the failure. 
          First Occurrence Data Capture (FODC) was invoked in 
the following 
          mode: "Automatic". FODC diagnostic information is 
located in the 
          following directory: 
 
"/db_log/userid/db2dump/FODC_Trap_2013-04-24-16.36.42.792877_000 
0/". 
DATA #1 : Signal Number Recieved, 4 bytes 
11 
DATA #2 : Siginfo, 128 bytes 
0x00007F981800FD70 : 0B00 0000 0000 0000 0100 0000 0000 0000 
................ 
0x00007F981800FD80 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FD90 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDA0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDB0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDC0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDD0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDE0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
 
2013-04-24-16.36.52.688762-240 I42506539E2268        LEVEL: 
Event 
PID     : 16424                TID : 140291218597632 PROC : 
db2sysc 0 
INSTANCE: userid               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-152                APPID: *N0.userid.130424203620 
AUTHID  : USERID               HOSTNAME: lab01 
EDUID   : 1373                 EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, oper system services, 
sqloPGRPRegisterOneCrash, probe:2154 
MESSAGE : lastCrashCount 
DATA #1 : unsigned integer, 8 bytes 
0 
DATA #2 : String, 10 bytes 
inRecovery 
DATA #3 : Boolean, 1 bytes 
false 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00007F9CD3BF05FE pdLog + 0x38E 
  [1] 0x00007F9CD604D25D sqloPGRPRegisterOneCrash + 0x17D 
  [2] 0x00007F9CD6093B11 sqloEDUCodeTrapHandler + 0x871 
  [3] 0x000000334C60F4A0 /lib64/libpthread.so.0 + 0xF4A0 
  [4] 0x00007F9CD4B473E4 _Z8sqlrirelP8sqlrr_cb + 0x84 
  [5] 0x00007F9CD6F24DC6 _Z8sqlriag2P8sqlrr_cb + 0x376 
  [6] 0x00007F9CD4B371C8 
_Z19sqlriExecSargThreadP8sqlrr_cbP12sqlri_opparm + 0x38 
  [7] 0x00007F9CD4B3709C 
_Z30sqlriPDGroupInvokePostPDThreadP8sqlrr_cbP21sqlriPushdownGrou 
pObjPi + 0x3C 
  [8] 0x00007F9CD6F24D59 _Z8sqlriag2P8sqlrr_cb + 0x309 
  [9] 0x00007F9CD6D7D5DB 
_Z16sqldEvalDataPredP13SQLD_DFM_WORKPmP10SQLD_DPRED + 0x19B 
  [10] 0x00007F9CD6F576EA 
_Z8sqlsfetcP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL 
Z_RIDPc + 0xC2A 
  [11] 0x00007F9CD6F2FFF3 _Z10sqlriFetchP8sqlrr_cbP9sqlri_taol + 
0x183 
  [12] 0x00007F9CD6F3F114 _Z7sqlritaP8sqlrr_cb + 0x514 
  [13] 0x00007F9CD6F331BD 
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x1AD 
  [14] 0x00007F9CD62DDA6D _Z16sqlrr_dss_routerP8sqlrr_cb + 0x6CD 
  [15] 0x00007F9CD4A85E8E 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x4BE 
  [16] 0x00007F9CD3EBD4E2 
/db_config/userid/sqllib/lib64/libdb2e.so.1 + 0x12184E2 
  [17] 0x00007F9CD3EBC743 _Z21sqleProcessSubRequestP8sqeAgent + 
0xE3 
  [18] 0x00007F9CD3ED6E04 _ZN8sqeAgent6RunEDUEv + 0x604 
  [19] 0x00007F9CD4EBC213 _ZN9sqzEDUObj9EDUDriverEv + 0xF3 
  [20] 0x00007F9CD4EBC119 _Z10sqlzRunEDUPcj + 0x9 
  [21] 0x00007F9CD4948FC1 sqloEDUEntry + 0x2A1 
  [22] 0x000000334C6077F1 /lib64/libpthread.so.0 + 0x77F1 
  [23] 0x000000334C2E570D clone + 0x6D
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 10.5 Fix Pack 3                        * 
****************************************************************
Local Fix:
workaround: 
It may be possible to rewrite the query text to avoid the 
correlation and/or the listener TQ.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem Fixed In DB2 Version 10.5 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
28.02.2014
28.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList