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 IC84326 Status: Closed

LATCH LEAKED MESSAGES IN THE LOGS DUE TO LATCH
SQLO_LT_SQLE_FEDFMP_APP_CB__FMPAPPLATCH

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 agent holds latch of SQLO_LT_SQLE_FEDFMP_APP_CB__fmpAppLatch 
when the corresponding application is in UOW-Waiting state. 
 
Similar messages will be reported in the db2diag.log: 
 
2012-01-12-17.38.53.158901-360 E9618409A422       LEVEL: Severe 
PID     : 1274692              TID  : 5320        PROC : db2sysc 
INSTANCE: xxxxxxx              NODE : 000 
EDUID   : 5320                 EDUNAME: db2agent (idle) 
FUNCTION: DB2 UDB, oper system services, 
sqloDumpLatchTableToLog, probe:10 
DATA #1 : String, 92 bytes 
Latch leaked on EDU termination: File sqle_fed_fmp.C : Line 487 
(Identity: 278) HoldCount: 1 
 
From the output of db2pd -stack for that agent, you can see 
below latch holding message: 
 
Holding Latch type: (SQLO_LT_SQLE_FEDFMP_APP_CB__fmpAppLatch) - 
Address: (780000000bfe508), Line: 481, File: sqle_fed_fmp.C 
HoldCount: 1 
 
This can happen when a busy application is forced, or killed or 
brought down by any other methods. This issue exists in the 
version after DB2 V9.7. This is specific to federated. And the 
error can happen when data source of Federation server is 
non-DRDA.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Federated user.                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* No workaround available, so please upgrade to the lattest    * 
* fixpack level.                                               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 V10.1 Fixpack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
17.12.2012
17.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList