home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC63920 Status: Closed

RUNSTATS CRASHES WHEN COLLECTING STATISTICS ON A STAT VIEW HAVING A
COLUMN WITH A NAME OF 128 CHARACTERS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The error occurs when the view has a column with a name of the 
maximum length - 128 characters. 
 
The stack is something like: 
 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x820F0002 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 
bytes 
0x00002aaac9be9400 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x00002AAAC9BE93E8 : 5858 5858 5858 5858 5858 5858 5858 5858 
XXXXXXXXXXXXXXXX 
0x00002AAAC9BE93F8 : 5858 5858 5858 5858 
XXXXXXXX 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x00002AAAC9BE9400 : 5858 5858 5858 5858 5858 5858 5858 5858 
XXXXXXXXXXXXXXXX 
0x00002AAAC9BE9410 : 5858 5858 5858 5858 5858 5858 5858 5858 
XXXXXXXXXXXXXXXX 
0x00002AAAC9BE9420 : 5858 5858 5858 5858 5858 5858 5858 5858 
XXXXXXXXXXXXXXXX 
CALLSTCK: 
 [0] 0x00002AAAAB9862C2 pdLog + 0x398 
[1] 0x00002AAAAD2DCDBC 
/home/db2inst/sqllib/lib64/libdb2e.so.1 + 0x25FEDBC 
 [2] 0x00002AAAADF84D40 sqlofmblkEx + 0x84A 
[3] 0x00002AAAAB96050C _Z9sqlofmblkPv + 0x6 
[4] 0x00002AAAAD44D89B 
_Z17sqlrStatViewStatsP8sqlrr_cbP10SQLD_TSTATP8sqlrg_pdPhiS5_i + 
0x5C1 
 [5] 0x00002AAAAD47614B 
_Z17sqlrLocalRunstatsP8sqlrr_cbP11sqlrrstringS2_S2_httPP8sqlrg_p 
diiiiP16sqlrl_stats_colsPPsjPPtjdjtPP20sqlr_runstats_resultS8_m 
+ 0x1DE5 
 [6] 0x00002AAAAD47C429 
_Z8sqlrrstaP8sqlrr_cbP11sqlrrstringS2_S2_hhP17sqlrl_stats_parmsP 
KhPs 
+ 0x1159 
 [7] 0x00002AAAAD4A1850 _Z17sqlrr_runstats_DAP5sqldaP5sqlca + 
0x83E 
 [8] 0x00002AAAABAF4FA9 
_Z19sqlerKnownProcedureiPcPiP5sqldaS2_P13sqlerFmpTableP8sqeAgent 
P5sqlca 
+ 0x6B9 
 [9] 0x00002AAAABAF6A29 
_Z11sqlerCallDLP14db2UCinterfaceP9UCstpInfo + 0x3E1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The error occurs when the view has a column with a name of   * 
* the maximum length - 128 characters.                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Do not use column names of 128 characters in views.          * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem was first fixed in Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.10.2009
26.01.2010
25.01.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList