|
Problem IT01594
|
Status: Closed |
DB2 APPL FAILS WITH -4499 ERROR OR HANG SITUATION IF THE APPL IS USING MANY PARAMETERS, SPECIALLY OF ARRAY TYPE OR ROW TYPE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
db2 application may fail with -4499 error or go into hang
situation if the application is using many parameters, specially
of array type or row type.
For example, in jcc application case, it may fail with the
following error log in jcc trace.
[jcc] BEGIN TRACE_DIAGNOSTICS
[jcc][Thread:main][SQLException@d18bb87a] java.sql.SQLException
[jcc][Thread:main][SQLException@d18bb87a] SQL state = null
[jcc][Thread:main][SQLException@d18bb87a] Error code = -4499
[jcc][Thread:main][SQLException@d18bb87a] Message =
[jcc][t4][2036][11152][3.65.97] The length of the DSS is not 0
at the end of the parsing the same ID chain. ERRORCODE=-4499,
SQLSTATE=null
[jcc][Thread:main][SQLException@d18bb87a] Stack trace follows
com.ibm.db2.jcc.am.DisconnectRecoverableException:
[jcc][t4][2036][11152][3.65.97] The length of the DSS is not 0
at the end of the parsing the same ID chain. ERRORCODE=-4499,
SQLSTATE=null
at com.ibm.db2.jcc.am.cd.a(cd.java:319)
at com.ibm.db2.jcc.am.cd.a(cd.java:378)
at com.ibm.db2.jcc.t4.x.a(x.java:1221)
at com.ibm.db2.jcc.t4.x.w(x.java:1212)
at com.ibm.db2.jcc.t4.ab.b(ab.java:84)
at com.ibm.db2.jcc.t4.p.b(p.java:69)
at com.ibm.db2.jcc.t4.rb.c(rb.java:244)
at com.ibm.db2.jcc.am.lo.oc(lo.java:3439)
at com.ibm.db2.jcc.am.lo.tc(lo.java:3563)
at com.ibm.db2.jcc.am.lo.b(lo.java:4343)
at
com.ibm.db2.jcc.am.CallableStatement.hc(CallableStatement.java:1
18)
at
com.ibm.db2.jcc.am.CallableStatement.execute(CallableStatement.j
ava:97)
at test.Application.callSp(Application.java:117)
at test.Application.run(Application.java:130)
at test.Application.main(Application.java:141)
[jcc] END TRACE_DIAGNOSTICS
SQLDARD in DRDA dara through db2trc fmt -c shows wrong
extended length like 0x8432 and it should be 0x842E in this
scenario as blow.
SQLDARD OBJDSS (ASCII) ...
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF ...
0000 FFFFD05300038008 241100008432FF00 ...S....$....2.. ...
0010 0000000000000000 0700000000000000 ................ ...
0020 0000000000000000 CA00000000000200 ................ ...
...
NEXT DSS LOGICAL RECORD (ASCII) ...
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF ...
0000 043F595F4D4F4455 4C45000000000000 .?Y_MODULE...... ...
0010 0000000100000000 0000000000000000 ................ ...
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 Version 10.1 FixPack 5 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem was first fixed in Version 10.1 FixPack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.05.2014
14.07.2015
14.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
