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

DB2TRC MIGHT TRAP WHEN FORMATTING LONG CLI MESSAGE WHILE PARSING A TRACE
RECORD FOR SQLGETDIAGFIELDW

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
The db2trc executable that is shipped with the CLI/ODBC driver 
uses the "-cli" component customer formatter trace option by 
default when formatting a trace dump file ("format/fmt" 
command). 
 
 
If the trace dump contains a very long CLI message then db2trc 
might trap because of a corrupted stack. 
Note: The trap might also manifest in hang/looping within the 
SEGV signal handler. 
Such a long message text has been observed when parsing the 
trace dump record for a CLI SQLGetDiagFieldW() call. 
 
A stack trace gathered when running db2trc within a debugger 
like gdb shows: 
 
(gdb) run fmt ddntt.dmp ddntt.fmt 
Starting program: /workbig/user/clidriver/adm/db2trc fmt 
ddntt.dmp ddntt.fmt 
Trace truncated                   : NO 
Trace wrapped                     : NO 
Total number of trace records     : 44585 
 
Program received signal SIGSEGV, Segmentation fault. 
0x0000000000423c05 in sqltcliTrcFmt () 
(gdb) where 
#0  0x0000000000423c05 in sqltcliTrcFmt () 
#1  0x006400650073006e in ?? () 
#2  0x0069006800740020 in ?? () 
#3  0x0072007000200073 in ?? () 
... 
 
The top function will show sqltcliTrcFmt() while the rest of the 
call stack is corrupted.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 4.                       * 
****************************************************************
Local Fix:
run "db2trc fmt -ncf <dump file> <format file>" to avoid the 
trap
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2011
01.05.2011
01.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList