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

DB2 COREDUMP MAY BE MISSING ON LINUX IN COMPLEX TRAP SCENARIOS DUE TO NOT
SETTING PR_SET_DUMPABLE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2sysc is a setuid process.  On Linux the PR_SET_DUMPABLE 
setting must be modified in order to allow the generation of a 
coredump in the case of a crash.  Currently this setting is 
modified during the crash processing itself.  In some cases a 
second error may occur before reaching the point where 
PR_SET_DUMPABLE is modified, with the result that no coredump 
will be generated. 
 
This may impeded the diagnosing of DB2 crashes, which frequently 
require a coredump to analyze the memory contents at the time of 
the crash.  Coredumps are normally generated by default, and the 
cause of the omission may be difficult to understand.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Linux                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Use documented workaround                                    * 
****************************************************************
Local Fix:
A workaround is to set the system wide setting fs.suid_dumpable 
value to "1", i.e. 
sysctl -w fs.suid_dumpable=1
Solution
Problem first fixed in DB2 Version 10.1 Fix Pack 5
Workaround
See Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2015
13.07.2015
13.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