|
Problem IT33112
|
Status: Closed |
DB2 MIGHT TRAP DURING A ZIGZAG-JOIN
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Db2 might trap when performing a zigzag join in the following
stack:
sqldFixExistingTCB
sqldLockTableFixTCB
sqldScanOpen
sqlriopn
sqlritib
sqlriZZOpenDims
sqlriZZInit
sqlriZigZagJoin
sqlriSectInvoke
sqlrr_smp_router
sqlrr_subagent_router
IPRA.$sqleSubRequestRouter
sqleProcessSubRequest
sqeAgent::RunEDU
sqzEDUObj::EDUDriver
The db2diag.log message reports the following message:
2019-10-14-18.07.40.068924+120 I3097057A2174 LEVEL: Severe
PID : 15008212 TID : 69192 PROC : db2sysc
INSTANCE: db2jkl NODE : 000 DB : JKL
APPHDL : 0-55842 APPID: 10.18.114.70.40661.191014151404
UOWID : 352 ACTID: 216448
AUTHID : SAPSR3 HOSTNAME: hal9000
EDUID : 69192 EDUNAME: db2agnts (JKL) 0
FUNCTION: DB2 UDB, data management, sqldFixExistingTCB,
probe:13569
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 17 bytes
Expected TEMP TCB |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.6 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT33113 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.06.2020
31.03.2021
31.03.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
