Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66919 Status: Closed

JCC APPLICATION RETURN -4499 "UNSUPPORTED DDM OBJECT CODE
POINT:0X220A" WHILE PROPERTY DEFERPREPARES = TRUE

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
JCC Type 4 application return -4499 "Unsupported DDM object code 
point: 0x220a" while property deferPrepares = true and connect 
to iSeries through DB2 Connect. 
 
The code snippet may generate above error 
---------------------- 
String sql = "update test set col2 = ? " ; 
PreparedStatment st = con.prepareStatement (sql) ; 
java.math.BigDecimal val = new java.math.BigDecimal("300.20"); 
st.setBigDecimal(1,val) 
int rc = st.executeUpdate(); 
.... 
---------------------- 
 
Type 2 application connecting to iSeries directly works fine.
Problem Summary:
**************************************************************** 
USERS AFFECTED: 
Java application calling a setBigDecimal() function against 
the system which supported extended decimal precision. 
**************************************************************** 
PROBLEM DESCRIPTION: 
JCC Type 4 application return -4499 "Unsupported DDM object code 
point: 0x220a" while property deferPrepares = true and connect 
to iSeries through DB2 Connect. 
 
The code snippet may generate above error 
---------------------- 
String sql = "update test set col2 = ? " ; 
PreparedStatment st = con.prepareStatement (sql) ; 
java.math.BigDecimal val = new java.math.BigDecimal("300.20"); 
st.setBigDecimal(1,val) 
int rc = st.executeUpdate(); 
.... 
---------------------- 
 
Type 2 application connecting to iSeries directly works fine.
Local Fix:
set deferPrepares = false
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 Version V9.7 Fixpack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.03.2010
03.06.2010
03.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList