home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC83414 Status: Closed

CLPPLUS WILL NO LONGER THROW A JAVA.IO.CHARCONVERSIONEXCEPTION WHEN
PROCESSING INVALID CHARACTERS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
CLPPlus will throw a java.io.CharConversionException when it 
encounters invalid characters.  In most cases it is preferred 
that CLPPlus continue processing the line even if some 
characters are invalid.  CLPPlus will be modified to use Action 
Replace which will cause invalid characters to be replaced and 
processing to continue rather than throw a 
java.io.CharConversionException exception.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLPPlus Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 7.                       * 
****************************************************************
Local Fix:
The CLPPlus can be configured to use Action Replace by modifying 
clpplus launch file.  On Windows the clpplus is launched by the 
clpplus.bat file located in the sqllib/bin directory. 
Approximately 240 lines into the file is the following line. 
 
"%JAVA_PATH%" -classpath "%CP%" com.ibm.clpplus.CLPPlus %* 2>NUL 
 
Once you locate this line add the string 
-Ddb2.jcc.charsetDecoderEncoder=3 after the "%JAVA_PATH%" . 
 
Below is the line with the parameter added. 
 
"%JAVA_PATH%" -Ddb2.jcc.charsetDecoderEncoder=3 -classpath 
"%CP%" com.ibm.clpplus.CLPPlus %* 2>NUL 
 
On Linux and Unix the clpplus is launchedf from the clpplus file 
located in the instance owners home directory under sqllib/bin. 
Approximately 2 lines from the end of the file is the following. 
 
$JAVA com.ibm.clpplus.CLPPlus $* 2> /dev/null 
 
Once you locate this line add ? 
-Ddb2.jcc.charsetDecoderEncoder=3? after ?$JAVA?.  Below is the 
modified line. 
 
$JAVA -Ddb2.jcc.charsetDecoderEncoder=3 com.ibm.clpplus.CLPPlus 
$* 2> /dev/null 
 
Once the CLPPlus is restarted the invalid characters will be 
replaced and java.io.CharConversionExceptions will not occur.
available fix packs:
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in Version 9.7 Fix Pack 7.
Workaround
The CLPPlus can be configured to use Action Replace by modifying 
clpplus launch file.  On Windows the clpplus is launched by the 
clpplus.bat file located in the sqllib/bin directory. 
Approximately 240 lines into the file is the following line. 
 
"%JAVA_PATH%" -classpath "%CP%" com.ibm.clpplus.CLPPlus %* 2>NUL 
 
Once you locate this line add the string 
-Ddb2.jcc.charsetDecoderEncoder=3 after the "%JAVA_PATH%" .
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.05.2012
05.11.2012
05.11.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList