ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Lamey <cla...@localmatters.com>
Subject Re: "encoding not supported"-error using iBATIS with db2 on z/os
Date Wed, 21 Nov 2007 17:16:26 GMT
It looks like the parameters to the sqlmap are in an encoding that the db
doesn't support.  Most likely an extended character in one encoding that
isn't valid in another.

What encoding is the db using?

What encoding are the parameters coming in from?  Java will use UTF-8
internally, but if you're reading data from a file encoded with windows-1252
there could be a character causing trouble.

On 11/21/07 10:08 AM, "Ralf Assmann" <ralf.assmann@innovations.de> wrote:

> Hi there,
> we have the following problem using iBATIS on a local machine (win2000)
> connecting a database at a remote host (db2 on z/os). We are using a jcc
> type 4 driver of IBM.
> While calling the ...queryForList(...)-methode of iBATIS -
> queryForObject(...) will bring the same result/error -, the following
> error occurs:
> --- The error occurred in <xml-file>
> --- The error occurred while applying a parameter map.
> --- Check the <statement>-InlineParameterMap.
> --- Check the statement (query failed).
> --- Cause: com.ibm.db2.jcc.b.DisconnectException: encoding not
> supported!!  DB2ConnectionCorrelator: GA6F0608.G460.C188390D477C
> The iBATIS-error itself occurs in method executeQuery(...) of class
> SqlExecutor.class at line "ps.execute();".
> Using the same driver while preparing an own prepared statement and
> executing it (plain jdbc without iBATIS), everythings works well and the
> result will be delivered. So it seems not to be a driver error ...
> Does anyone has an idea what happens there?
> Many thanks.
> Ralf

View raw message