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 IT01911 Status: Closed

DB2LOOK MIGHT SEGV (COREDUMP) IF A TABLESPACE CONTAINS MORE THAN 30 STRIPES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Running db2look might generate a coredump with segv if one 
tablespace contains more than 30 stripes. 
The location of the crash might vary but here is one example 
from the core file: 
 
#0  0x000000000046f576 in ParseTablespaceMap() 
#1  0x000000000046eeb5 in ParseTablespaceNodeInfo() 
#2  0x000000000048e1a2 in ParseBuffer() 
#3  0x000000000048a995 in create_tablespace_ddl() 
#4  0x000000000041b188 in main () 
 
A trace output will show that db2look stopped processing at some 
point: 
 
560            0.100198000   | | | | | ParseTablespaceMap data 
[probe 30] 
561            0.100198000   | | | | | ParseTablespaceMap data 
[probe 50] 
562            0.100202000   | | | | | | ParseContainerInfo 
entry 
563            0.100202000   | | | | | | | FindElement entry 
564            0.100203000   | | | | | | | FindElement exit 
565            0.100203000   | | | | | | | FindElement entry 
566            0.100204000   | | | | | | | FindElement exit 
567            0.100206000   | | | | | | ParseContainerInfo exit 
568            0.100207000   | | | | | ParseTablespaceMap data 
[probe 30] 
569            0.100207000   | | | | | ParseTablespaceMap data 
[probe 50]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description above.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Solution
First fixed in Version V10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.05.2014
29.03.2015
29.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList