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

ERROR RAISED INCORRECTLY FROM SQLEFEDFMPMANAGER::DISCONNECT UPON SUBAGENT
CLEANUP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When a subagent working on behalf of a coordinator agent is 
cleanup up, it may get sent an interrupt signal 
depending on the code currently executing in that subagent's 
code path. 
 
If the subagent is also associated with a db2fmp process 
executing federated code, then this may lead to the following 
sequence of errors in the db2diag.log : 
 
2012-08-17-02.49.02.110085+060 I4453399E448        LEVEL: Severe 
PID     : 14992                TID  : 46920542185792PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-58304              APPID: 
9.10.11.12.34514.120817014904 
AUTHID  : DB2INST1 
EDUID   : 49486                EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqleFedFMPManager::disconnect, probe:30 
RETCODE : ZRC=0x00000048=72 
 
2012-08-17-02.49.02.110218+060 I4453848E451        LEVEL: Severe 
PID     : 14992                TID  : 46920542185792PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-58304              APPID: 
172.16.10.140.34514.120817014904 
AUTHID  : DB2INST1 
EDUID   : 49486                EDUNAME: db2agntp (SAMPLE) 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqleFedFMPManager::disconnect, probe:30 
RETCODE : ZRC=0xFFFFFB95=-1131 
 
This marks db2fmp as unstable and can lead to error SQL20357N 
failing a commit statement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.1 Fix Pack 3              * 
****************************************************************
Local Fix:
available fix packs:
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
This problem was first fixed in DB2 V10.1 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.04.2013
21.10.2013
21.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList