|
Problem IC99639
|
Status: Closed |
COLUMN BASED QUERY MAY HANG IF THE QUERY CONTAINS AGGREGATION FUNCTIONS AND DATA EXCEPTION OCCURS |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
A column based query may hang if it meets the following
conditions:
1. Containing aggregation functions such as group by, SUM etc.
2. Data exceptions may occur for aggregation functions e.g SUM
in the query has exceeded a data type limit (for example hitting
the maximum integer size)
During the hang period in db2pd -latch output, there are many
latch waiters waiting on
SQLO_LT_ibm_cde__query__GroupByControlBlock__mErrorAndWarningMut
ex latch, but there is no latch holder.
In db2diag.log, the similar messages may be observed.
2014-01-23-23.01.03.231194+480 E9934361A458 LEVEL:
Severe
PID : 13172852 TID : 388027 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
HOSTNAME: host1
EDUID : 388027 EDUNAME: db2agent (idle) 0
FUNCTION: DB2 UDB, oper system services,
sqloDumpLatchTableToLog, probe:10
DATA #1 : String, 102 bytes
Latch leaked on EDU termination: File GroupByControlBlock.hpp :
Line 2648 (Identity: 914) HoldCount: 1 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 fix pack 5 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Upgrade to DB2 version 10.5 fix pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.02.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
