LI73696: IN LINUX DB2SYSC CRASH (SIGNAL #11) DOES NOT CREATE CORE FILE EVENTHOUGH ULIMIT -C UNLIMITED.

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• In Linux db2sysc crash (Signal #11) does not create core file
  eventhough ulimit -c unlimited.
  
  Manually doing kill -11 twice against db2sys PID does not create
  core file. However it does with db2agent.
  

Local fix

• A workaround is to set suid_dumpable.
  
  # The suid_dumpable control file is found in different places
  ....
  
  if [ -e /proc/sys/kernel/suid_dumpable ] ; then
     echo 1 > /proc/sys/kernel/suid_dumpable
  else
     echo 1 > /proc/sys/fs/suid_dumpable
  
  NOTE that value of "1" means that the core is dumped by the
  current user. "2" is more restrictive, and allows only root to
  read the file. We use "1" in our prctl() call (which can be
  viewed as a security issue)
  To make the change permanent, add the following to
  /etc/sysctl.conf
  
  # Allow suid programs to dump core
  fs.suid_dumpable = 1
  

Problem summary

• IN LINUX DB2SYSC CRASH (SIGNAL #11) DOES NOT CREATE CORE FILE
  EVENTHOUGH ULIMIT -C UNLIMITED.
  

Problem conclusion

• Fixed in FP6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  LI73186

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R910 PSY

     UP