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 IT08192 Status: Closed

CRASH IN HASH JOIN UNION WHEN A QUERY IS INTERRUPTED - REGRESSION FIX FROM
IT03187

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The crash details might look  similar to following in the 
db2daig.log : 
 
015-03-17-19.44.05.665736-240 I60597975A1074     LEVEL: Error 
PID     : 7407                 TID  : 4397748709648PROC : 
db2sysc 0 
INSTANCE: db2inst1               NODE : 000         DB   : MYDB 
APPHDL  : 0-40439              APPID: <> 
AUTHID  :  <> 
EDUID   : 404                  EDUNAME: db2agntp (MYDB) 0 
FUNCTION: DB2 UDB, sort/list services, sqlsFetchNextTempRecord, 
probe:499 
MESSAGE : ZRC=0x80130003=-2146238461=SQLS_INTRP "Interrupt. 
User Cancel." 
          DIA8003C The interrupt  has been received. 
DATA #1 : Codepath, 8 bytes 
1 
DATA #2 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x80130003 
DATA #3 : SQLS_MBUFS, PD_TYPE_SQLS_MBUFS, 1464 bytes 
 
.... 
 
2015-03-17-19.45.13.750990-240 I60607086A503      LEVEL: Severe 
PID     : 7407                 TID  : 4397786458384PROC : 
db2sysc 0 
INSTANCE: db2inst1               NODE : 000         DB   : MYDB 
APPHDL  : 0-40267              APPID: <> 
AUTHID  : <> 
EDUID   : 28                   EDUNAME: db2agent (MYDB) 0 
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, 
probe:10 
MESSAGE : DIA0505I Execution of a component signal handling 
function has begun. 
 
2015-03-17-19.45.13.751081-240 I60607590A229      LEVEL: Severe 
PID:7407 TID:4397786458384 NODE:000 Title: **** DRDA ASCB **** 
Dump File: 
<>/sqllib/db2dump/FODC_Trap_2015-03-17-19.45.13.635462_0000/7407 
.28.000.dump.bin 
 
 
The stack trace will have following functions : 
 
0x000003FFF97F9ECE _ZN11sqkfChannel15lockChannelArgsEPKci + 
0x0056 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFF97F3FCA 
_ZN11sqkfChannel13ReceiveBufferEPP10sqkfBufferi + 0x009e 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFF98301EA 
_Z8sqlkqrcvP7sqlkqcbP8sqeAgentPiPP10sqkfBufferS3_ + 0x0236 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFF983B092 _Z8sqlktrcvP9sqlri_taoPi + 0x007a 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFF983DDB4 
_Z18sqlkt_unpack_tupleP9sqlri_taoPiS1_P5sqlcaPjS4_ + 0x0660 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFF98369E0 _Z8sqlktftcP8sqeAgentP9sqlri_taoP5sqlcaPjS5_ 
+ 0x0574 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFFB0EC2E4 _Z8sqlritqaP8sqlrr_cb + 0x01c8 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
0x000003FFFB13423E _Z9sqlrihsjnP8sqlrr_cb + 0x0842 
                (/apps/mtdbp7/sqllib/lib64/libdb2e.so.1) 
... 
 
If a query is interrupted while running  a plan similar to 
following  it  can cause similar  crash, 
                hsjn 
              / 
         union 
  +--------+--------+ 
blah 
 | 
 TQ 
 
This is  a regression from the  APAR IT03187 
 
INTRA_PARALLEL  have to be ON to hit this issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 11 or higher.                   * 
****************************************************************
Local Fix:
Solution
The problem is first fixed in DB2 V9.7 Fix Pack 11.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.04.2015
09.10.2015
09.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList