|
Problem IT09222
|
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 / A50 - 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 systems running on the Linux platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* This is a serviceability improvement only. Upgrade to DB2 *
* Version 10.5 Fix Pack 7 or implement the 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.5 Fix Pack 7 |
| Workaround |
see Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.06.2015
16.02.2016
16.02.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
