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

RLSCONV REUSE AND SQLSTT ARE WRONGLY RETURNED AGAINST UNIT OF WORK
COMMITTED SYNCTYPE IN RECEIVED RQSDSS ON XA INTERFACE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During XA transaction processing, RLSCONV REUSE and SQLSTT are 
wrongly returned after Unit of work committed SYNCTYPE is 
received in RQSDSS, then it can induce the "DSS chained with 
same id at end of same id chain parse. ERRORCODE=-4499" error on 
the client. 
 
  In the case of a jcc application, we can see the following 
exception. 
 
  Exception message = [jcc][2035][11153][3.61.75] DSS chained 
with same id at end of same id chain parse. ERRORCODE=-4499, 
SQLSTATE=null 
  com.ibm.db2.jcc.am.DisconnectRecoverableException: 
[jcc][2035][11153][3.61.75] DSS chained with same id at end of 
same id chain parse. ERRORCODE=-4499, SQLSTATE=null 
        at com.ibm.db2.jcc.am.ed.a(ed.java:317) 
        at com.ibm.db2.jcc.am.ed.a(ed.java:356) 
        at com.ibm.db2.jcc.t4.z.a(z.java:1170) 
        at com.ibm.db2.jcc.t4.z.w(z.java:1164) 
        at com.ibm.db2.jcc.uw.UWReply.e(UWReply.java:372) 
        at com.ibm.db2.jcc.t4.o.e(o.java:54) 
        at com.ibm.db2.jcc.t4.b.zb(b.java:2565) 
        at com.ibm.db2.jcc.am.jb.o(jb.java:1105) 
        at com.ibm.db2.jcc.am.jb.i(jb.java:1034) 
        at com.ibm.db2.jcc.t4.b.i(b.java:5000) 
        at com.ibm.db2.jcc.am.jb.j(jb.java:1041) 
        at com.ibm.db2.jcc.am.vm.k(vm.java:616) 
        at com.ibm.db2.jcc.am.vm.d(vm.java:510) 
        at com.ibm.db2.jcc.am.vm.c(vm.java:414) 
        at com.ibm.db2.jcc.am.vm.next(vm.java:308) 
 
 
  "db2trc fmt -c" output shows the following information during 
the problem reproduction. 
 
4739237 data DB2 UDB DRDA Communication Manager sqljcReceive fnc 
(3.3.54.3.0.1178) 
    pid 4063270 tid 55101 cpid 9371728 node 0 sec 7525616 nsec 
751238230 probe 1178 
    bytes 48 
 
    RECEIVE BUFFER(AS): 
 
            SYNCCTL RQSDSS                   (ASCII) 
(EBCDIC) 
         0 1 2 3 4 5 6 7  8 9 A B C D E F   0123456789ABCDEF 
0123456789ABCDEF 
  0000  001FD00100010019 1055000511870300   .........U...... 
..}..........g.. 
  0010  081801FFFFFFFF00 08190310000000     ............... 
............... 
 
  DDM Format: d0 RECV(AS) RQSDSS - Request Data Stream Structure 
  LL: 31  CORR: 0001  CHAINED: n  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: n 
 
    NM: SYNCCTL - Sync Point Control Request 
      LL: 25    CP: 1055 
      NM: SYNCTYPE - Sync Point Operation Type 
        LL: 5    CP: 1187 
        Unit of work committed (0X03) 
      NM: XID - Transaction Indentifier (XID) 
        LL: 8    CP: 1801 
        DATA: FFFFFFFF 
      NM: XAFLAGS - XA Flags 
        LL: 8    CP: 1903 
        FLAGS: 10000000 
          Local Transaction 
 
 
4739370 data DB2 UDB DRDA Communication Manager sqljcSend fnc 
(3.3.54.5.0.1177) 
    pid 4063270 tid 55101 cpid 9371728 node 0 sec 7525616 nsec 
751365812 probe 1177 
    bytes 87 
 
    SEND BUFFER(AS): 
 
            SYNCCRD OBJDSS                   (ASCII) 
(EBCDIC) 
         0 1 2 3 4 5 6 7  8 9 A B C D E F   0123456789ABCDEF 
0123456789ABCDEF 
  0000  0017D05300010011 1248000819040000   ...S.....H...... 
..}............. 
  0010  00000005119FF2                      ....... 
......2 
 
            SQLSTT OBJDSS                    (ASCII) 
(EBCDIC) 
         0 1 2 3 4 5 6 7  8 9 A B C D E F   0123456789ABCDEF 
0123456789ABCDEF 
  0000  002FD00300010029 2414FF000000001F   ./.....)$....... 
..}............. 
  0010  5345542043555252 454E542053434845   SET CURRENT SCHE 
.........+...... 
  0020  4D41203D20224143 30312020202022     MA = "xxxx    " 
(.............. 
 
  DDM Format: d0 SEND(AS) OBJDSS - Object Data Stream Structure 
  LL: 23  CORR: 0001  CHAINED: y  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: y 
 
    NM: SYNCCRD - Sync Point Control Reply 
      LL: 17    CP: 1248 
      NM: XARETVAL - XA return Value 
        LL: 8    CP: 1904 
        OK (0) 
      NM: RLSCONV - Release Conversation 
        LL: 5    CP: 119F 
        RLSCONV REUSE 
 
  DDM Format: d0 SEND(AS) OBJDSS - Object Data Stream Structure 
  LL: 47  CORR: 0001  CHAINED: n  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: n 
 
    NM: SQLSTT - SQL Statement 
      LL: 41    CP: 2414 
      DATA:                              (ASCII) 
(EBCDIC) 
      FF000000001F5345 542043555252454E  ......SET CURREN 
...............+ 
      5420534348454D41 203D202241433031  T SCHEMA = "xxxx 
......(......... 
      2020202022                             "            .....
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* XA transaction user                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During XA transaction processing, RLSCONV REUSE and SQLSTT   * 
* arewr ongly returned after Unit of work committed SYNCTYPE   * 
* is re ceived in RQSDSS, then it can induce the "DSS chained  * 
* with sa me id at end of same id chain parse.                 * 
* ERRORCODE=-4499" error onth e client.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.7 FixPak 5                          * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 FixPak 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.03.2011
15.12.2011
15.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.5 FixList