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

DB2DIAG TRAPS WHEN THE TOTAL NUMBER OF ROTATING DB2DIAG.#.LOG FILES UNDER
ALL THE SPLIT DIAGPATH DIRECTORIES EXCEEDS 15

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2diag traps when the total number of rotating db2diag.#.log 
files under all the split diagpath directories exceeds 15. 
with following stacktrace: 
 
Program terminated with signal 11, Segmentation fault. 
#0  0x000000000041ea35 in pdDiagPopulateFilenamesForFacility () 
(gdb) where 
#0  0x000000000041ea35 in pdDiagPopulateFilenamesForFacility () 
#1  0x0000000000428f78 in pdDiagGetDiagFiles () 
#2  0x000000000040de49 in pdDiagSetOptions () 
#3  0x0000000000408a35 in main () 
(gdb)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fixpack 5 or higher.             * 
****************************************************************
Local Fix:
Manage to keep the total number of rotating db2diag.#.log files 
under all the split diagpath directories within 15.
Solution
First fixed in DB2 Version 10.1 Fixpack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.06.2014
14.07.2015
14.07.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