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 IT00465 Status: Geschlossen

XA application may be failed by receiving -998

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
XA application may be failed by receiving -998 at 
sqlrr_rollback_with_sqlcode. We may see below message on 
db2diag.log. 
----- 
2014-02-27-13.11.17.181954+540 I259040365E885        LEVEL: 
Warning 
PID     : 2533                 TID : 139656117085952 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : XXXX 
 
APPHDL  : 0-26920              APPID: 
192.168.0.1.50521.140225043940 
AUTHID  : DB2INST1             HOSTNAME: makuhari 
EDUID   : 41                   EDUNAME: db2agent (XXXX) 0 
FUNCTION: DB2 UDB, relation data serv, 
sqlrr_rollback_with_sqlcode, 
probe:150 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -998   sqlerrml: 2 
 
 sqlerrmc: 5 
 sqlerrp : SQLQ0290 
 sqlerrd : (1) 0x8026006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 58005 
 
2014-02-27-13.11.17.243103+540 I259041251E629        LEVEL: 
Error 
PID     : 2533                 TID : 139656117085952 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : XXXX 
 
APPHDL  : 0-26920              APPID: 
192.168.0.1.50521.140225043940 
AUTHID  : DB2INST1             HOSTNAME: makuhari 
EDUID   : 41                   EDUNAME: db2agent (XXXX) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrxreg, probe:10 
RETCODE : ZRC=0x80100027=-2146435033=SQLP_PROTO 
          "Transaction manager function called in wrong 
context." 
          DIA8039C XA error with request type of "". XA protocol 
error. 
-----
Problem-Zusammenfassung:
ERROR DESCRIPTION: 
XA application may be failed by receiving -998 at 
sqlrr_rollback_with_sqlcode. We may see below message on 
db2diag.log. 
----- 
2014-02-27-13.11.17.181954+540 I259040365E885        LEVEL: 
Warning 
PID     : 2533                 TID : 139656117085952 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : XXXX 
 
APPHDL  : 0-26920              APPID: 
192.168.0.1.50521.140225043940 
AUTHID  : DB2INST1             HOSTNAME: makuhari 
EDUID   : 41                   EDUNAME: db2agent (XXXX) 0 
FUNCTION: DB2 UDB, relation data serv, 
sqlrr_rollback_with_sqlcode, 
probe:150 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -998   sqlerrml: 2 
 
 sqlerrmc: 5 
 sqlerrp : SQLQ0290 
 sqlerrd : (1) 0x8026006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 58005 
 
2014-02-27-13.11.17.243103+540 I259041251E629        LEVEL: 
Error 
PID     : 2533                 TID : 139656117085952 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : XXXX 
 
APPHDL  : 0-26920              APPID: 
192.168.0.1.50521.140225043940 
AUTHID  : DB2INST1             HOSTNAME: makuhari 
EDUID   : 41                   EDUNAME: db2agent (XXXX) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrxreg, probe:10 
RETCODE : ZRC=0x80100027=-2146435033=SQLP_PROTO 
          "Transaction manager function called in wrong 
context." 
          DIA8039C XA error with request type of "". XA protocol 
error. 
-----
Local-Fix:
Lösung
The probelm is fixed in 10.5 FP5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.03.2014
14.07.2015
14.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList