Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC64367 Status: Closed

RUNSTAT ON XML DATA MAY REPORT WARNING IN
FUNCTIONXMLRNSTATS::SUMMARIZEBCATCHALLPV()

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
While running runstats on xml tables we may receive following in 
db2diag.log file. 
 
================================ 
2009-09-03-10.55.31.720092+120 I2037449E857        LEVEL: 
Warning 
PID     : 1379                 TID  : 46920529602880PROC : 
db2sysc 0 
INSTANCE: inst1              NODE : 000          DB   : SAMPLE 
APPHDL  : 0-321                APPID: *LOCAL.abcd.090903085300 
AUTHID  : Admin 
EDUID   : 114                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, XML Node Manager, 
XmlrnStatsSummarizeBCatchAllPV, 
probe:1976 
DATA #1 : String, 16 bytes 
Sample Node Card 
DATA #2 : unsigned integer, 8 bytes 
0 
DATA #3 : String, 15 bytes 
Sample Doc Card 
DATA #4 : unsigned integer, 8 bytes 
0 
DATA #5 : String, 14 bytes 
Sum Node Count 
DATA #6 : unsigned integer, 4 bytes 
1206532352 
DATA #7 : String, 13 bytes 
Sum Doc Count 
DATA #8 : unsigned integer, 4 bytes 
1185276928 
DATA #9 : String, 20 bytes 
Distinct Value Count 
DATA #10: unsigned integer, 8 bytes 
632 
 
 
This messages are not harmful for the system,these will be 
reported as a info message as a fix of this APAR in future 
releses.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* RUNSTAT ON XML DATA MAY REPORT WARNING                       * 
* INFUNCTIONXMLRNSTATS::SUMMARIZEBCATCHALLPV()                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack  2                   * 
****************************************************************
Local Fix:
available fix packs:
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 6 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 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

Solution
Problem was first fixed in Version 9.7 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.11.2009
31.05.2010
31.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList