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

DB MAY ABEND WHILE EXECUTING AN OLAP QUERY WITH A BOUNDED WINDOW
AGGREGATION RANGE GROUPING.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The database may abend when an OLAP query is executed: 
The query must have the following: 
1. Be a Range window grouping 
2. The range must be bounded 
3. There must be an order by clause as part of scalar 
aggregation 
 
The stack trace observed is as follows: 
<stacktrace> 
 
sqlng_build_SCALAG_op 
sqlng_process_mate_op 
sqlng_process_pipe_op 
sqlng_process_mate_op 
sqlng_process_pipe_op 
sqlng_process_return_op 
sqlng_build_thread 
 
sqlng_main 
sqlnn_cmpl 
.... 
</stacktrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* V95fp7                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The database may abend when an OLAP query is executed:       * 
*                                                              * 
* The query must have the following:                           * 
*                                                              * 
* 1. Be a Range window grouping                                * 
*                                                              * 
* 2. The range must be bounded                                 * 
*                                                              * 
* 3. There must be an order by clause as part of scalar        * 
*                                                              * 
* aggregation                                                  * 
*                                                              * 
*                                                              * 
*                                                              * 
* The stack trace observed is as follows:                      * 
*                                                              * 
* <stacktrace>                                                 * 
*                                                              * 
*                                                              * 
*                                                              * 
* sqlng_build_SCALAG_op                                        * 
*                                                              * 
* sqlng_process_mate_op                                        * 
*                                                              * 
* sqlng_process_pipe_op                                        * 
*                                                              * 
* sqlng_process_mate_op                                        * 
*                                                              * 
* sqlng_process_pipe_op                                        * 
*                                                              * 
* sqlng_process_return_op                                      * 
*                                                              * 
* sqlng_build_thread                                           * 
*                                                              * 
*                                                              * 
*                                                              * 
* sqlng_main                                                   * 
*                                                              * 
* sqlnn_cmpl                                                   * 
*                                                              * 
* ....                                                         * 
*                                                              * 
* </stacktrace>                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v95fp8                                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Program defect
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73541 IC73569 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.12.2010
05.07.2011
05.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList