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

DB2FMP MAY LEFT FOREVER WHEN "CONNECT RESET" HAPPENED AND THE
DB2FMP IS IN THE HEADER OF THE FED FMP PRCOCESS LIST

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The Non-threaded federated db2fmp process may be left and never 
be reused even the corresponding connection is closed when 
following conditions are satified: 
1. It is in the header of the federated fmp proc list 
2. One or more federated fmp process(es) is/are in abnormal 
status before its connection is closed. 
 
To reproduce: 
 
1) Open Two sessions and query a nicname 
    session 1   --> db2fmp  pid_1 
    session 2   --> db2fmp  pid_2 
 
2)  db2fmpterm  pid_2   ( flag becomes to 0x00000154) 
    session 2:  db2 connect reset     (db2fmp  pid_2  terminated 
) 
    session 1:  db2 connect reset     (db2fmp  pid_1  left ) 
 
3)  Open some other sessions:   pid_1 left but can never be 
resued
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The users are running a non-threaded fenced wrapper.         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 FP5.                                        * 
****************************************************************
Local Fix:
Solution
The problem is firstly fixed on V10.1 FP5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.03.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList