Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 18739 invoked from network); 14 Jul 2009 14:10:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jul 2009 14:10:56 -0000 Received: (qmail 30990 invoked by uid 500); 14 Jul 2009 14:11:05 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 30949 invoked by uid 500); 14 Jul 2009 14:11:05 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 30820 invoked by uid 99); 14 Jul 2009 14:11:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 14:11:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jeffgbutler@gmail.com designates 209.85.222.196 as permitted sender) Received: from [209.85.222.196] (HELO mail-pz0-f196.google.com) (209.85.222.196) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 14:10:55 +0000 Received: by pzk34 with SMTP id 34so1017875pzk.4 for ; Tue, 14 Jul 2009 07:10:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=jsQdT5a2RoqZkEXNen+3o3aQETzrNg6vnN2jWwnOGaY=; b=qB0Yi1rsNlVd4+EtUXRjYVsEMYib5/Yz4Q70zys4QH/VmRb08Xt6hprDsw+m1JnQFI 1sXJiof4KRxBkWAUBJiOtdJgY6DmNwZe5AiNBISkYrIGWn/CM+fsP1ah2LrJMvf/Vuuh ir/iNyL3sYuIgt1IqYCf2uSXiVm7iVj1SVJ5c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=w8q0Ynzeh9qcUqIXn4i9b6BFTSyFfVRTcDajUqqEgj+o4lzlRF2Q5qfT4liJndw8yo CrhF6NHyWP9QILGX8wFkirdqAAKYdTQ1s5wEb5vR+9oPZd3p9Zq7T31oP/OBsHe6BOlm aoIqz4mQ0OZRxfz6l0tTp76x5/fRX+CG4n5vc= MIME-Version: 1.0 Received: by 10.142.238.20 with SMTP id l20mr1567175wfh.116.1247580634291; Tue, 14 Jul 2009 07:10:34 -0700 (PDT) In-Reply-To: References: Date: Tue, 14 Jul 2009 09:10:34 -0500 Message-ID: Subject: Re: error fetching BLOB and CLOB data From: Jeff Butler To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=000e0cd17e78891f73046eab000a X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd17e78891f73046eab000a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Where in the iBATIS code is this happening? You haven't given us much to go on - perhaps an abbreviated stack trace would be in order? Jeff Butler On Tue, Jul 14, 2009 at 8:58 AM, Pat Thatte wrote: > Thanks Mario. We are using a "CLI-based Type 2 JDBC Driver" which uses > jdbc 2.0. > > We eliminated the driver as an issue, as I mentioned in my question, by > using the same datasource with straight SQL. We were able to successfully > fetch BLOB and CLOB with straight SQL instead of iBATIS. > > Any other suggestions would be appreciated. > > > > Subject: Re: error fetching BLOB and CLOB data > > > > Pat, > > > > looks like you are using a very old version of the DB2 JDBC driver > (atleast > > in the iBatis use-case u have detailed below) > > a - which is not a type 4 JDBC driver > > b - is a JDBC v1 driver. > > > > The versions of DB2 i have seen, dont even ship with that JDBC driver > > anymore. However here is a link that should be describing your env and > what > > u need to do - http://www-01.ibm.com/support/docview.wss?uid=swg21081165 > > > > > > Mario > > > > > --------------------------------------------------------------------------- > > > > Pat Thatte > > > > Subject : error fetching BLOB and CLOB data > > > > > > We have BLOBs and CLOBs in a DB2 v8 database. We use a jdbcType of 'BLOB' > > or 'CLOB' respectively in our SQL Map file and are getting an error > > 'CLI0123E SQL data type out of range. SQLSTATE=HY004'. > > > > There was an older post about checking the driver type, but we are able > to > > fetch the data with the same DataSource using straight SQL. > > > > What else could we look at? > > > > Thanks, > > Pat. > --000e0cd17e78891f73046eab000a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Where in the iBATIS code is this happening? =A0You haven't given us muc= h to go on - perhaps an=A0abbreviated=A0stack trace would be in order?
=
Jeff Butler

On Tue, Jul 14= , 2009 at 8:58 AM, Pat Thatte <pat4520@hotmail.com> wrote:
Thanks Mario. We are using a "CLI-based Type 2 JDBC Driver" which= uses jdbc 2.0.

We eliminated the driver as an issue, as I mentione= d in my question, by using the same datasource with straight SQL. We were a= ble to successfully fetch BLOB and CLOB with straight SQL instead of iBATIS= .

Any other suggestions would be appreciated.


> Subject: Re= : error fetching BLOB and CLOB data

>
> Pat,=
>
> looks like you are using a very old version of the DB2 JD= BC driver (atleast
> in the iBatis use-case u have detailed below)
> a - which is n= ot a type 4 JDBC driver
> b - is a JDBC v1 driver.
>
>= The versions of DB2 i have seen, dont even ship with that JDBC driver
> anymore. However here is a link that should be describing your env and= what
> u need to do - http://www-01.ibm.com/support/d= ocview.wss?uid=3Dswg21081165
>
>
> Mario
> =
> = -----------------------------= ----------------------------------------------
> =
> Pat Thatte =
> =
> = Subject : error fetching BLOB and CLOB data
> =
>
> We have BLOBs and CLOBs in a DB2 v8 database. We use a jdbcTy= pe of 'BLOB'
> or 'CLOB' respectively in our SQL Map = file and are getting an error
> 'CLI0123E SQL data type out of ra= nge. SQLSTATE=3DHY004'.
>
> There was an older post about checking the driver type, but w= e are able to
> fetch the data with the same DataSource using straigh= t SQL.
>
> What else could we look at?
>
> Thanks= ,
> Pat.

--000e0cd17e78891f73046eab000a--