home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT07942 Status: Geschlossen

WHEN (SPECIAL)REGISTERS ARE SET IN CLI, PROTOCOL IS VIOLATED FOR XA
TRANSACTION IN FEDERATION ENVIRONMENT.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
DB2 federation fails with sql0998 error due to violation of 
protocol for distributed transaction processing. 
 
When special registers are set by users for connection in 
federation setup, SQL statements fails with -998 error due to 
invalid transaction state. 
The error happens due to violation of distributed transaction 
processing protocol in db2 where the special register settings 
erroneoulsy marks the beginning of DUOW when in fact 
the first explicit SQL after the connection establishment should 
mark the beginning of DUOW.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 7                   * 
****************************************************************
Local-Fix:
To avoid the issue not to have special register for federated 
setup. 
For example: if the issue is caused by CurrentFunctionPath 
parameter, remove CurrentFunctionPath from CLI cfg and 
amend the app so that it calls all catalogued routines 
explicitly i.e. "CALL CLS.sp_foo" rather than "CALL sp_foo".
Lösung
Problem was first fixed in DB2 Version 10.5 and Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.03.2015
19.01.2016
27.04.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList