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

IF THE ROW WIDTH PROCESSED BY A PARTIAL AGGREGATION OPERATOR IS MORE THEN
32K THEN WE COULD GENERATE INCORRECT RESULTS

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
IF THE ROW WIDTH GOING THROUGH A pGRPBY (PARTIAL AGGREGATION
OPERATOR  ) IS MORE THEN 32K
AND SORTHEAP IS SUFFICIENTLY LARGE
THEN SOMETIMES Db2  COULD RETURN INCORRECT RESULTS  .

example of plan:

       8.33333
       RETURN
        ( 1)
       84.626
         |
       8.33333
        GRPBY
        ( 2)
       84.6256
         |
       8.33333
        SCAN
        ( 3)
       84.5942
         |
       8.33333
        SORT
        ( 4)
       84.5938
         |
       8.33333
       pGRPBY
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* See Error Description and install fixpak with this fix.      *
****************************************************************
Local Fix:
Disable partial aggregation by the following :   db2set
DB2_REDUCED_OPTIMIZATION="NO_PEA,NO_PED"
recycle the instance
This is an internal registry variable setting to workaround this
problem.
The setting should be removed upon upgrade to the Fix pack level
containing this fix :
db2set DB2_REDUCED_OPTIMIZATION=
recycle the instance
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.03.2020
30.06.2020
30.06.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)