|
Problem IT31324
|
Status: Closed |
DB2 CLP FRONT END MIGHT HANG IN CLP_FP_SIG->SQLNLSMESSAGE AND LOCK DB2DIAG.LOG FILE
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
This scenario is similar with IT23978, while in this APAR,
futher fix more user generated signals, such as SIGHUP/SIGINT,
etc.
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
pdLogSysRC
sqlodque
clp_fp_exitlist
sqlnlsFreeMsgFileList |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* n/a *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.1 or v11.5 with the latest fixpack level. *
**************************************************************** |
| Local Fix: |
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. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* n/a *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.1 or v11.5 with the latest fixpack level. *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.12.2019
12.03.2020
12.03.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
