IBM Known Issues for DB2 on Linux - United States  TECHNOTE (FAQ)

QUESTION
 What are known issues on Linux platforms related to DB2® database products ? 

ANSWER
Known Issues with DB2 on Linux 

[/support/docview.wss?uid=swg21681093&amp;aid=1]
Bug ID [/support/docview.wss?uid=swg21681093&amp;aid=2]Description
Linux Flavor [/support/docview.wss?uid=swg21681093&amp;aid=3]
Comments 1076574 DB2's 'db2syc' process exhibits memory leak. Redhat v6 DB2 'db2sysc' process will see memory leak. Eventually, RAM and swap will be 100% consumed. The machine will be non-responsive. This memory is released when DB2 engine is stopped with 'db2stop'.

This is a RedHat Linux issue and is discussed here:https://access.redhat.com/support/cases/01054560/ [https://access.redhat.com/support/cases/01054560/] 

This problem is already fixed by RedHat. The detailed description of all the Redhat Linux versions affected by this bug and fix details are available at:https://rhn.redhat.com/errata/RHBA-2014-0470.html [https://rhn.redhat.com/errata/RHBA-2014-0470.html] 1042807 32-bit applications running on 64-bit platforms where issuing msgrcv with -ve message type hangs with error: 
error: msgrcv: No message of the desired type. Redhat v7
kernel-3.10.0-54.0.1.e17.x86_64 32-bit application does not work on RHEL 7.0 with 64-bit DB2 engine. When the sample programs under sqllib/samples/c/ like inattach.c or dbinfo.c is compiled by bldapp with BITWIDTH=32, it hangs in sqlorqueInternal.

This is a RedHat Linux issue and is discussed here:
https://access.redhat.com/solutions/1202773 [https://access.redhat.com/solutions/1202773]

This problem will be fixed by RedHat in v7.1 1264533 DB2 Panic, due to removed IPC resources. Redhat v7.2 The problem is caused by logind removing IPC resources owned by user when this user logs off. The bug is described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1264533 [https://bugzilla.redhat.com/show_bug.cgi?id=1264533]

Local Fix:
Add the following setting to file /etc/systemd/logind.conf
RemoveIPC=no 948149 db2dart reports incorrect container tag for container which resides on XFS SLES 12 This problem exists for XFS and only if container is opened in Direct IO mode. In reality the container tag is not corrupted but result buffer will return empty after pread call, which did not report any errors. More information here:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=131069 [https://bugzilla.linux.ibm.com/show_bug.cgi?id=131069] 

The problem is fixed in 
kernel-default-3.12.32-33.1.x86_64.rpm

1165277 db2 local connections may hang in semop function Redhat/CentOS v6.6. The problem is caused by a IPC bug, first seen in kernel kernel 2.6.32-434.el6. More information here: https://bugzilla.linux.ibm.com/show_bug.cgi?id=119049 [https://bugzilla.linux.ibm.com/show_bug.cgi?id=119049]

Fixed in https://rhn.redhat.com/errata/RHSA-2015-1272.html [https://rhn.redhat.com/errata/RHSA-2015-1272.html]

Local Fix:
Configure local clients' connections through TCP/IP loopback.
RHEL7.2: CF servers crashed when db2cluster -cm -list -alert command issued Environment: DB2 11.1 GA / RHEL7.2

Whenever I execute "db2cluster -cm -list -alert", 0x80090030 logged in db2diag.log on member nodes. Finally CF servers become STOPPED status with high probability.

  2016-09-12-15.51.35.731323+540 I362836576E602       LEVEL: Severe  
  PID     : 22991                TID : 70366596624816 PROC : db2sysc 0  
  INSTANCE: db2inst1             NODE : 000           DB   : SAMPLE
  HOSTNAME: pscale00.ibm.com  
  EDUID   : 112                  EDUNAME: db2LLMn2 (SAMPLE) 0  
  FUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876  
  DATA #1 : <preformatted>  
  NotifyConn_t.wait (PsGetNotification:) failed: 0x80090030  
  DATA #1 : <preformatted>  
  If a CF return code is displayed above and you wish to get  
  more information then please run the following command:  
    
  db2diag -cfrc <CF_errcode> 
Add the following setting to file /etc/systemd/logind.conf
RemoveIPC=no