| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC82318 | Status: Closed |
SQL EXECUTED BY JDBC DRIVER RESULTS IN DUMP FILES CREATED AND DB 2DIAG.LOG FILE SHOWING INVALID SQL STATEMENT LENGTH FOR SQL > 2M | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
Submit any SQL statement which is more than 2MB size will result
in dump files and db2diag.log entries.
JCC driver should return -101 error code if detects SQL > 2MB.
db2diag.log file shows:
2012-02-07-23.00.02.672004-360 E84642A777 LEVEL: Error
PID : 4915368 TID : 38558 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-19010 APPID:
192.168.1.10.53281.120207194544
AUTHID : DB2USER
EDUID : 38558 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsParseSqlSttGrpNOC,
probe:419
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected.
The diagnostic data returned is (SRVDGN):
"FUNCTION ID = 0050 , PROBE POINT = 0419 ,
TRACE POINT = 0015 ,
SUBCODE1 = FFFFFFFF804B0095,
SUBCODE2 = 0000000000251A6B,
SUBCODE3 = 0000000000251A6B,
ERROR MSG = Parser: Invalid SQL statement length".
2012-02-07-23.00.02.672374-360 I85420A626 LEVEL: Error
PID : 4915368 TID : 38558 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-19010 APPID: 192.168.1.10.53281.120207194544
AUTHID : DB2USER
EDUID : 38558 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsParseSqlSttGrpNOC,
probe:15
MESSAGE : ZRC=0x804B0095=-2142568299=SQLJS_VALNSP "VALUE ERROR"
DATA #1 : DDM Object, PD_TYPE_DDM_OBJECT, 16 bytes
data length : 2431595
codepoint : 0x2414 ( SQLSTT )
length : 8 ( EXTENDED )
2012-02-07-23.00.02.672645-360 I86047A186 LEVEL: Error
PID :4915368 TID:38558 NODE:000 Title: **** DRDA ASCB ****
Dump File:
/db2/db2inst1/sqllib/db2dump/4915368.38558.000.dump.bin
This apar fix is contained with the jcc driver 3.64.82 that
shipped with v97fp6, not within the db2 server itself. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of the Universal JDBC driver * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6 (JCC driver version * * 3.64.82) * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
Problem First fixed in DB2 Version 9.7 Fix Pack 6 (JCC driver version 3.64.82) | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC86205 IC86208 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.03.2012 12.02.2013 20.03.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6, 9.7.FP7 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|