|
Problem IC69477
|
Status: Geschlossen |
UNIVERSAL JDBC TYPE 4 APPLICATION RECEIVES ERROR. A DRDA DATA STREAM SYNTAX ERROR WAS DETECTED. REASON: 0X2. ERRORCODE=-4499 |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
V9.7 Fixpak 1 client running a JDBC Type 4 application receives
DRD Data Stream Syntax error. Reason: 0x2. ERRORCODE=-4499,
SQLSTATE=58009.
This is a boundary condition which
only occurs when dealing with a large number of columns, input
or output, such that the length of the SQLDARD is exactly 65518
bytes. (Two DSS where the first DSS length is X'FFFF and the
second DSS length is X'7FFFF).
This problem occurs with a large number of columns, such that
the describe information for the columns expand exactly 2
complete, full drda blocks.
---- Begin backtrace for Nested Throwables
com.ibm.db2.jcc.am.uo: [jcc][t4][2034][11148][4.8.87] Execution
failed due to a distribution protocol error that caused
deallocation of the
conversation. A DRDA Data Stream Syntax Error was detected.
Reason: 0x2. ERRORCODE=-4499, SQLSTATE=58009
at com.ibm.db2.jcc.am.gd.a(gd.java:317)
at com.ibm.db2.jcc.am.gd.a(gd.java:365)
at com.ibm.db2.jcc.t4.cb.l(cb.java:942)
at com.ibm.db2.jcc.t4.cb.e(cb.java:324)
at com.ibm.db2.jcc.t4.cb.d(cb.java:259)
at com.ibm.db2.jcc.t4.fb.b(fb.java:2672)
at com.ibm.db2.jcc.t4.fb.a(fb.java:2630)
at com.ibm.db2.jcc.t4.fb.a(fb.java:172)
at com.ibm.db2.jcc.t4.fb.b(fb.java:83)
at com.ibm.db2.jcc.t4.t.b(t.java:69)
at com.ibm.db2.jcc.t4.vb.c(vb.java:242)
at com.ibm.db2.jcc.am.xm.mc(xm.java:2891)
at com.ibm.db2.jcc.am.xm.pc(xm.java:2997)
at com.ibm.db2.jcc.am.xm.vc(xm.java:3126)
at com.ibm.db2.jcc.am.xm.a(xm.java:547)
at com.ibm.db2.jcc.am.lb.a(lb.java:2183)
at com.ibm.db2.jcc.am.lb.a(lb.java:2142)
at com.ibm.db2.jcc.am.lb.prepareStatement(lb.java:1688)
at com.ibm.db2.jcc.am.bf.prepareStatement(bf.java:243)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.pmiPrepareStatement(W
SJdbcConnection.java:2503) |
| Problem-Zusammenfassung: |
Fixed in DB2 V9.5 FP7 JDBC driver. |
| Local-Fix: |
|
| Lösung |
Upgrade DB2 JDBC driver to V9.5 FP7. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 29.06.2010
26.03.2014
26.03.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP7
|
| Problem behoben lt. FixList in der Version |
