Latest versionsfixlist
11.1.0.6 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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC80932 Status: Closed

Error "The DDM parameter value is not supported" when you try to
insert LOB data into a column that is not wide enough for it.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
If a JDBC (Java Database Connectivity) application calls the 
executeBatch method of a Statement object and one of the SQL 
commands in the batch tries to insert LOB data into a column 
that is not wide enough for it, the error message does not say 
correctly why the error occurred. 
 
An application using the IBM Data Server Driver for JDBC and 
SQLJ (also known as the JCC driver) ought to throw an exception 
with message like this: 
 
"Error for batch element #[...]: DB2 SQL Error: SQLCODE=-302, 
SQLSTATE=22001" 
 
That is, the message ought to include "SQLCODE=-302" (which is 
equivalent to SQL0302N). 
 
Because of this defect the application gets an exception with a 
message like this instead: 
 
"Error for batch element #[...]: The DDM parameter value is not 
supported.  DDM parameter code point having unsupported value : 
[...]. 
An input host variable may not be within the range the server 
supports. ERRORCODE=-4499, SQLSTATE=58017" 
 
Because of this defect, messages like this appear in db2diag.log 
on 
the database server: 
 
 9999-31-12-23.59.99.999999+999 XXXXXXXXXXXX      LEVEL: Error 
 PID    : XXXXX                TID  : XXXXX      PROC :db2sysc 0 
 INSTANCE: XXXXXXXX            NODE : 999        DB   :XXXXXXXX 
 APPHDL  : XXXXXXX 
APPID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
 AUTHID  : XXXXXXXX 
 EDUID  : XXXXX                EDUNAME: db2agent (XXXXXXXX) 0 
 FUNCTION: DB2 UDB, DRDA Application Server, 
sqljsParseExtendedLength, probe:409 
 MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected. 
 The diagnostic data returned is (SRVDGN): "FUNCTION ID = 0051 , 
PROBE POINT = 0409 , 
 TRACE POINT = 0030 , SUBCODE1 = 000000000000087D, 
 SUBCODE2 = 0000000000000341, SUBCODE3 = 0000000000000881, 
 ERROR MSG = Parser: 
          Invalid DDM Extended Length". 
 
 9999-31-12-23.59.99.999999+999 XXXXXXXXXXXX      LEVEL: Error 
 PID    : XXXXX                TID  : XXXXX      PROC : 
 db2sysc 0 
 INSTANCE: XXXXXXXX            NODE : 999        DB  : XXXXXXXX 
 APPHDL  : XXXXXXX 
APPID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
 AUTHID  : XXXXXXXX 
 EDUID  : XXXXX                EDUNAME: db2agent (XXXXXXXX) 0 
 FUNCTION: DB2 UDB, DRDA Application Server, 
 sqljsParseExtendedLength, probe:30 
 MESSAGE : ZRC=0x804B0095=-2142568299=SQLJS_VALNSP "VALUE ERROR" 
 DATA #1 : DDM Object, PD_TYPE_DDM_OBJECT, 16 bytes 
 
 
At a minimum, this APAR fix should be applied on the database 
server.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows who run an          * 
* application that uses the IBM Data Server Driver for JDBC    * 
* and SQLJ                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in Version 9.5 Fix Pack 10. 
At a minimum, this fix should be applied on the database server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2012
29.08.2012
29.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.