|
Problem IC65503
|
Status: Geschlossen |
HIGH CPU USAGE IN A SCENARIO WITH TABLE QUEUE SPILLING |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
The mechanism that is used to flow rows between agents in a DPF
environment is called tablequeues. There exists a flow control
mechanism to regulate the flow of rows called a tablequeue spill
that will decide to defer the sending of data by spilling it
into a temp table.
In a configuration with many database partitions, for example,
over 50 partitions or so, then due to this defect there may be
some logic that does unnecessary work thereby driving up the cpu
usage.
If stacks are collected for an agent that is trying to resend
spilled buffers, the function "StartSpillResends" might be seen
in this scenario as being a large consumer of cpu cycles.
This fix will rework the logic in a way that will remove the
unneeded work and help alleviate the cpu usage. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* DPF with large node config (100+) *
****************************************************************
* PROBLEM DESCRIPTION: *
* High cpu usage during tablequeue spilling. *
****************************************************************
* RECOMMENDATION: *
* Install fixpack 6 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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
|
| Lösung |
fix is contained in v95FP6 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC65555 IZ68053
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 11.01.2010
13.05.2010
13.05.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
