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 IC62680 Status: Geschlossen

IN DB2 V9.1 AND V9.5, THE PERCENT_ROWS_SELECTED COLUMN IN
SYSIBMADM.APPL_PERFORMANCE MAY RETURN VALUES THAT ARE TOO LARGE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In DB2 V9.1 and V9.5, the PERCENT_ROWS_SELECTED column in the 
SYSIBMADM.APPL_PERFORMANCE table may return values that are too 
large for the numeric datatype.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The PERCENT_ROWS_SELECTED column in the                      * 
* SYSIBMADM.APPL_PERFORMANCE table may return values that are  * 
* too                                                          * 
* large for the numeric datatype.                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to V9.7 FP1.                                          * 
****************************************************************
Local-Fix:
A work around is to create your SQL to use the appl_performance 
view but do the aggregation per agentid on both rows_selected 
and rows_read for each node. Then do an 'IF' stmt in the SQL 
where if rows_read = 0 then percentage = 0 else (aggregate 
rows_select / aggregate rows_read) * 100 is the percentage.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
DB2 V9.7 FP1 will contain the fix.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.08.2009
17.02.2010
17.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList