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

POOL_XDA_L_READS AND POOL_XDA_P_READS COLUMNS OF SYSIBMADM.SNAPDB SEEMS TO
BE REVERSE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
POOL_XDA_L_READS and POOL_XDA_P_READS columns of view 
SYSIBMADM.SNAPDB seems to be reverse. Seems, there is a miss 
assignment of the values to  the column names in 
SYSIBMADM.SNAPDB in V9.7. 
 
The get snasphot for database output retrieves the following 
counters : 
db2 get snapshot for database on sample | grep xda 
 
Buffer pool xda logical reads              = 97 
 
Buffer pool xda physical reads             = 22 
 
Buffer pool temporary xda logical reads    = 0 
 
Buffer pool temporary xda physical reads   = 0 
 
Buffer pool xda writes                     = 34 
 
Asynchronous pool xda page reads           = 0 
 
Asynchronous pool xda page writes          = 0 
 
Asynchronous xda read requests             = 0 
 
 
If we compare with sysibmadm.snapdb information, the logical and 
 physical read counters for xda data are wrong. 
 
db2 "select POOL_XDA_L_READS ,POOL_XDA_P_READS  from 
sysibmadm.snapdb" 
 
POOL_XDA_L_READS       POOL_XDA_P_READS 
--------------------------        -------------------- 
 
    22                                             97
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* POOL_XDA_L_READS and POOL_XDA_P_READS columns of view        * 
* SYSIBMADM.SNAPDB seems to be reverse. Seems, there is a miss * 
* assignment of the values to  the column names in             * 
* SYSIBMADM.SNAPDB in V9.7.                                    * 
*                                                              * 
* The get snasphot for database output retrieves the following * 
* wrong counters :                                             * 
*                                                              * 
* db2 get snapshot for database on sample | grep xda           * 
*                                                              * 
* Buffer pool xda logical reads              = 97              * 
*                                                              * 
* Buffer pool xda physical reads             = 22              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The customer has to include this fix . The fix is going to   * 
* release in V97FP3.                                           * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The Fix is going to include in the V97FP3. 
 
The customer will see the correct order values of 
POOL_XDA_L_READS and POOL_XDA_P_READS after including the fix.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69656 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.04.2010
09.05.2011
09.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.4 FixList