|
Problem IC91455
|
Status: Geschlossen |
ERROR RAISED INCORRECTLY FROM SQLEFEDFMPMANAGER::DISCONNECT UPON SUBAGENT CLEANUP |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade the database server to V10.1 Fix Pack 3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
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
|
| Lösung |
This problem was first fixed in DB2 V10.1 Fix Pack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 10.04.2013
21.10.2013
21.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
