DB2 - Problem description
Problem IC95353 | Status: Closed |
RUNSTATS ON XML COLUMNS PRODUCES INAPPROPRIATE WARNING LEVEL DIAGNOSTIC MESSAGES. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When collecting statistics on xml columns, the RUNSTATS utility logs inappropriate diagnostic messages. These messages are informational only, and should not have been logged as warnings. The FUNCTION area of the messages will show sqlr_init_tstat with different probe numbers. One example is: 2013-05-19-00.01.23.710459-240 I3584706A811 LEVEL: Warning PID : 17563742 TID : 36788 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB APPHDL : 0-354 APPID: *LOCAL.myapp.130519040103 AUTHID : db2inst1 EDUID : 36788 EDUNAME: db2agent (MYDB) 0 FUNCTION: DB2 UDB, relation data serv, sqlr_init_tstat, probe:13234 DATA #1 : String, 17 bytes statHeapAutomatic DATA #2 : Boolean, 1 bytes true DATA #3 : String, 13 bytes min_pool_size DATA #4 : unsigned integer, 8 bytes 16992 DATA #5 : String, 5 bytes hpmin DATA #6 : unsigned integer, 4 bytes 2813424 DATA #7 : String, 5 bytes hpmax DATA #8 : unsigned integer, 4 bytes 2813424 DATA #9 : String, 14 bytes stat_heap_size DATA #10: unsigned integer, 8 bytes 17956864 This problem was first introduced in DB2 Version 9.7 Fixpack 6. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.5 FP3 * **************************************************************** | |
Local Fix: | |
There is no facility to disable just these warnings from sqlr_init_tstat while maintaining DIAGLEVEL 3. | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem Fixed In DB2 v10.5 FP3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 21.04.2014 21.04.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |