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

DB2 MAY ABEND WHEN A PLAN CONTAINING AGGREGATION IS INTERRUPTED AND
SUBSEQUENTLY REEXECUTED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 may abend or trap when a plan containing aggregation is 
interrupted or otherwise terminated abnormally and then executed 
again such that the section is reused. To hit the trap there 
must be rows flowing through the aggregation operator when the 
interrupt is received and then when the section is reused there 
must be no rows flowing through the aggregation operator. 
 
You may see a stack similar to : 
 
sqlriPeaEOF 
sqlripea 
sqlriSectInvoke 
sqlrr_dss_router 
 
A match to this APAR will have sqlriPeaEOF at the top of the 
stack
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to latest fixpack, 105fp9 or later                   * 
****************************************************************
Local Fix:
setting DB2_REDUCED_OPTIMIZATION=NO_PEA will work around the 
issue. Static sections must be rebound for it to take effect
Solution
fix will be delivered into 105fp9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.04.2017
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)