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

Crash with SIGSEGV in function sqlrivsum when using SUM and GROUPY with a
subselect that contains UNNEST.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A query that uses SUM, GROUP BY and UNNEST can trap with a 
SIGSEGV if the SUM is applied as a vector aggregation. 
To cause the trap, a query must be issued and has a SUM and 
GROUP BY with a sub-select that contains UNNEST, an example: 
 
SELECT sum(c1) 
FROM    ( SELECT t.c1 
     FROM UNNEST(arrgv1) AS t (c1) ) 
GROUP BY c1@ 
 
This will cause a trap with SIGSEGV with sqlrivsum on the top of 
the stack as a result of bad input going into the vector sum. 
 
Stack example: 
 
 
sqlrivsum 
sqlsVectorize 
sqlsChecknVectorize 
sqlsopen 
sqlrsopen 
sqlrsopen 
sqlrisrt 
sqlriunn 
sqlriset 
sqlriSectInvoke 
sqlrr_process_fetch_request 
sqlrr_fetch 
sqljs_ddm_cntqry 
sqljsParseRdbAccessed 
sqljsParse.fdpr.clone.104 
sqljsSqlam 
sqljsDriveRequests 
sqljsDrdaAsInnerDriver 
RunEDU 
EDUDriver 
sqloEDUEntry
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 10.1 fix pack 5                   * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 UDB Version 10.1 fix pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.01.2015
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList