home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT10391 Status: Closed

SEMAPHORES NOT CLEARED WHEN A NON-TRAP THREAD EXITS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In db2diag.log, we see the following : 
 
2015-06-19-09.31.48.642672+480 I392122183A333     LEVEL: Severe 
PID     : 9766086              TID  : 1800        PROC : db2fmp 
(C) 0 
INSTANCE: db2inst1            NODE : 000 
EDUID   : 1800                 EDUNAME: db2fmp (C) 0 
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFedFmpListener, 
probe:20 
RETCODE : ZRC=0xFFFFFB95=-1131 
 
2015-06-19-09.31.49.026970+480 I392122517A465     LEVEL: Warning 
PID     : 9766086              TID  : 1800        PROC : db2fmp 
(C) 0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 1800                 EDUNAME: db2fmp (C) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : Thread of db2fmp terminated with nonzero rc 
DATA #1 : Hexdump, 4 bytes 
0x000000011114458C : FFFF FB95 
.... 
 
In a rare scenario, where a IPC error is raised at the right 
place, an agent that is attempting to execute an external 
threadsafe  stored procedure/udf could hang while waiting for 
the FMP thread to respond, but the FMP thread is already 
terminated. The hang is on the particular agent, but it could be 
more severe in the case of federated FMP, as the agent could be 
holding on to some latches.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Version below V9.7 FixPack 12                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP12                                     * 
****************************************************************
Local Fix:
A workaround for this is to use 
db2fmpterm to kill the particular FMP, which will trigger sysc 
to do cleanup and wake up the hanging agent.
Solution
Fixed in DB2 V9.7 FP12
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

28.07.2015
10.02.2016
10.02.2016
Problem solved at the following versions (IBM BugInfos)
9.7.FP12
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList