Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT06419 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 10.1 fix pack 5                   * 
****************************************************************
Local-Fix:
Lösung
Problem was first fixed in DB2 UDB Version 10.1 fix pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.01.2015
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList