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

WHEN CONFIGURING DEBUG MODE FOR DB2TOP AND $HOME/.DB2TOPRC VARIABLE
STREAMSIZE EQUAL 100.0M, db2top crashes

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
Configuring .db2toprc -> streamsize=100.0M and environment 
variable MALLOC_CHECK_=3, when he run db2top it core dumps 
generating the output "coreinfo.txt". 
 
 
Note2: If you do not configure env as above db2top runs normally 
 
When configuring debug mode for db2top and $HOME/.db2toprc 
variable streamsize equal 100.0M, and environment variable 
MALLOC_CHECK_ equal 3, db2top crashes.
Problem-Zusammenfassung:
Problem Description: 
WHEN CONFIGURING DEBUG MODE FOR DB2TOP AND $HOME/.DB2TOPRC VARIA 
BLE STREAMSIZE EQUAL 100.0M, AND ENVIRONMENT VARIABLE MALLOC_CHE 
Problem Summary: 
Configuring .db2toprc -> streamsize=100.0M and environment 
variable MALLOC_CHECK_=3, when he run db2top it core dumps 
generating the output if file "41150.665.706coreinfo.txt". I 
tested and yes, the output reproduces as Mr. Bossut explained. 
 
Note2: If you do not configure env as above db2top runs normally 
 
When configuring debug mode for db2top and $HOME/.db2toprc 
variable streamsize equal 100.0M, and environment variable 
MALLOC_CHECK_ equal 3, db2top crashes.
Local-Fix:
Do not use debug mode
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in Version 9.5 Fix Pack 6
Workaround
Do not use debug mode
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC65714 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.09.2009
13.05.2010
28.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version