DB2 FOR LUW / DB2FORLUW / A50 - DB2

The db2support with -fodc option might get sigsegv, like as 
below: 
 
$ db2support -fodc 
Trap on 11, pid:47055310: Generating trap file and core file in 
db2dump directory 
 
The app_trap.txt under sqllib/db2dump shows information like as 
below: 
 
 DB2 USERS : 
 ----------- 
 A db2support process terminated abnormally. 
 This may have been caused by a prog- 
 ramming error in the routine. 
 A stack trace-back follows. 
 
</Siginfo_t> 
Signal #11 (SIGSEGV): si_addr is 0x1000000000000000, si_code is 
0x00000032 (SEGV_MAPERR:Address not mapped to object.) 
</SignalDetails> 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0000000100019B68 strncpy + 0xE8 
 
This problem happens only when all the conditions are met: 
 
a) getaddrinfo() returns short name to ai_canonname instead of 
fully qualified domain name. 
b) db2nodes.cfg contains more than one line.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2support with -fodc option.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.5 FixPack 5 or later.              * 
****************************************************************

db2support -fodc -member <member#> or db2support

This problem was first fixed in DB2 V10.5 FP5.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.07.2014
31.03.2015
31.03.2015