DB2 - Problembeschreibung
Problem IT07332 | Status: Geschlossen |
DB2 COREDUMP MAY BE MISSING ON LINUX IN COMPLEX TRAP SCENARIOS DUE TO NOT SETTING PR_SET_DUMPABLE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
Lösung | |
Problem first fixed in DB2 Version 10.1 Fix Pack 5 | |
Workaround | |
See Local Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.02.2015 13.07.2015 13.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |