DB2 FOR LUW / DB2FORLUW / A50 - DB2

Under rare timing conditions, when Db2 CLP front end process
(db2) receives a signal whilst terminating, it might hang with
sqlnlsMessage->sqlnlscmsg functions on the top of the stack,
e.g.:

ossLockGetConflict
sqlnlscmsg
sqlnlsMessage
sqlnlsgmsg
sqlogmsg
pdLoadMessage
pdGetMessage
pdLogInternal
pdLogSysRC
sqloLogAndMapQueError
sqlodque
clp_fp_exitlist
clp_fp_sig

munmap
_ossMemFree
sqlnlsFreeMsgFileList

Typically the hang involves SIGHUP, which is generated by the
operating system when the terminal, from which Db2 CLP was run,
is closed. As the result, Db2 CLP process will be stuck, holding
a lock on the db2diag.log and/or administration notification
log. This will cause other processes trying to write to the log
file to fail with SQLO_SHAR error. Performance of the tools,
which write to db2diag.log like e.g. RUNSTATs, might be affected
once the problem is exposed.
Problem is specific to UNIX platforms and Db2 Version 10.5 Fix
Packs 8 and 9.

****************************************************************
* USERS AFFECTED:                                              *
* UNIX                                                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 version 10.5 Fix Pack 10 or higher.           *
****************************************************************

If SQLO_SHAR on one of the log files is observed, one should
check whether the file is being used by some process using OS
tools like fuser/lsof. When process using the file is
identified, OS tools like procstack/gstack can be used to
generate a backtrace (stack) to verify whether it matches this
APAR.
To resolve the problem, one can either:
a) kill PID of Db2 CLP front that got stuck
$ kill -9 
b) rename the log file held by the stuck CLP.

not known / see Local fix

forerunner  : IT20290 
follow-up : PH06246 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

07.02.2018
16.07.2018
06.12.2018