|
Problem IC97093
|
Status: Geschlossen |
LARGE SORT HEAP USAGE WHEN 0-CARDINALITY INDICATED ON SORT OPERATION |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 *
* Fix Pack 4 or higher. *
**************************************************************** |
| Local-Fix: |
|
| Lösung |
Update the DB2 Linux, Unix, Windows server to Version 10.1
Fix Pack 4 or higher. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.10.2013
31.10.2017
31.10.2017 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
