home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC93275 Status: Geschlossen

LARGE SORT HEAP USAGE WHEN 0-CARDINALITY INDICATED ON SORT OPERATION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DB2 will use large the fully confirgured amount of SORT HEAP 
when 0-cardinality is indicated on a SORT operation. 
 
The issue can be identified by examining the query access plan, 
and 
looking for a SORT with a 0 estimated cardinality.  Typically a 
0-cardinality function, table, global temporary table, or 
session temporary table can cause this plan. 
 
In Access plan : 
 3) SORT  : (Sort) 
  Cumulative Total Cost:   22.6971 
  Cumulative CPU Cost:   126925 
  Cumulative I/O Cost:   2.9975 
  Cumulative Re-Total Cost:  0.0097435 
  Cumulative Re-CPU Cost:  34379.9 
  Cumulative Re-I/O Cost:  0 
  Cumulative First Row Cost:  22.6971 
  Estimated Bufferpool Buffers:  2.9975 
 
  Arguments: 
  --------- 
  BUFFSORT: (Sort for Buffering Rows) 
   TRUE 
  DUPLWARN: (Duplicates Warning flag) 
   FALSE 
  NUMROWS : (Estimated number of rows) 
   0 <--------------------------------0 cardinality estimated. 
  ROWWIDTH: (Estimated width of rows) 
   424 
  SORTKEY : (Sort Key column) 
   NONE 
  TEMPSIZE: (Temporary Table Page Size) 
   4096 
  UNIQUE  : (Uniqueness required flag) 
   FALSE
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users with large sort heap configured and 0-cardinality  * 
* tables                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update the DB2 Linux, Unix, Windows server to Version 9.7    * 
* Fix                                                          * 
* Pack 9 or higher.                                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Update the DB2 Linux, Unix, Windows server to Version 9.7 Fix 
Pack 9 or higher.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC97093 IC97099 IT00554 IT00555 IT00556 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.06.2013
24.03.2014
24.03.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.0.,
9.7.
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList