Fixes are available
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
Rational Application Developer for WebSphere Software, Version 7.0.0.8
6.1.1.8: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 8
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Default mapping of DB2 v9.1 XML column to java.lang.String field results in "Invalid type mapping exist for attribute: <colName> in file: DB2UDBNT_V91_1. Add converter or change the data type" Default mapping to java.lang.String will continue but validation error will be corrected allowing ejbdeloy to successfully complete. EJB deployment code will use PreparedStatement.getString() and PreparedStatement.setString() against the JDBC driver when reading/writing to a column of this type.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * Toolkit v6.1.1 and Rational Application * * Developer v7.0 * **************************************************************** * PROBLEM DESCRIPTION: A DB2 v9.1 XML column being mapped to * * a java.lang.String enterprise bean * * field causes a validation error. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 v9.1 XML column being mapped to a java.lang.String enterprise bean field causes the following validation error: Invalid type mapping exist for attribute: <columnName> in file: DB2UDBNT_V91_1. Add converter or change the data type This is happening because the underlying enterprise bean mapping functionality does not provide support for the DB2 v9.1 XML column type.
Problem conclusion
Support for the DB2 v9.1 XML column type mapping to a java.lang.String EJB field has been added. The fix for this APAR is currently targeted for inclusion in the WebSphere Application Server Toolkit fixpack 6.1.1.8 and Rational Application Developer fixpack 7.0.0.8. Please refer to the following Recommended Updates page for WebSphere Application Server Toolkit delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980 and the following Recommended Updates page for Rational Application Developer delivery information: http://www.ibm.com/support/docview.wss?uid=swg27007823
Temporary fix
Comments
APAR Information
APAR number
PK68767
Reported component name
WEBAPP SERVER A
Reported component ID
5724J0820
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-09
Closed date
2008-10-08
Last modified date
2008-10-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBAPP SERVER A
Fixed component ID
5724J0820
Applicable component levels
R610 PSY
UP
Document Information
Modified date:
29 December 2021