DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver

Jim McAlpine

DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
We have a JDBC application which is getting the following when accessing a
LOB table -

com.ibm.db2.jcc.am.SqlException: [jcc][10120][11936][3.59.81] Invalid
operation: Lob is closed. ERRORCODE=-4470, SQLSTATE=null
The application works against DB2 for z/OS V8 but fails against V9. I have
downloaded the latest JCC JARs but I'm still getting the same error.

I found some hits with google but none that seem to relate to DB2 for z/OS.
I didn't find apar relating to this error.

Anyone seen this error before.

Jim McAlpine

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
Mentoring should be a rewarding experience for everyone...
IDUG is offering up to 80% off when you both come to the conference!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Edward Long

Re: DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
(in response to Jim McAlpine)
Hi Jim.
There are a set of custom properties that affect the way LOBS get processed by JDBC.
 
To avoid the -4470, and several other user experiences, we have to use the following:
fullyMaterializeLobData=true
fullyMaterializeInputStreams=true
progressiveStreaming=2
progressiveLocators=2
webSphereDefaultIsolationLevel=2
The capitalizations are required. Depending upon whether you use WebSphere, Tomcat or horse and buggy will alter how you define these properties. 

Edward Long

--- On Tue, 11/16/10, Jim McAlpine <[login to unmask email]> wrote:


From: Jim McAlpine <[login to unmask email]>
Subject: [DB2-L] DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
To: [login to unmask email]
Date: Tuesday, November 16, 2010, 11:28 AM



We have a JDBC application which is getting the following when accessing a LOB table -
 
com.ibm.db2.jcc.am.SqlException: [jcc][10120][11936][3.59.81] Invalid operation: Lob is closed. ERRORCODE=-4470, SQLSTATE=null

The application works against DB2 for z/OS V8 but fails against V9.   I have downloaded the latest JCC JARs but I'm still getting the same error.
 
I found some hits with google but none that seem to relate to DB2 for z/OS.  I didn't find apar relating to this error. 
 
Anyone seen this error before.
 
Jim McAlpine
 




The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are not already an IDUG member, please register here.

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
Mentoring should be a rewarding experience for everyone...
IDUG is offering up to 80% off when you both come to the conference!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Jim McAlpine

Re: DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
(in response to Edward Long)
On Tue, Nov 16, 2010 at 4:42 PM, Ed Long <[login to unmask email]> wrote:

> Hi Jim.
> There are a set of custom properties that affect the way LOBS get processed
> by JDBC.
>
> To avoid the -4470, and several other user experiences, we have to use the
> following:
> fullyMaterializeLobData=true
> fullyMaterializeInputStreams=true
> progressiveStreaming=2
> progressiveLocators=2
> webSphereDefaultIsolationLevel=2
> The capitalizations are required. Depending upon whether you use WebSphere,
> Tomcat or horse and buggy will alter how you define these properties.
>
> Edward Long
>

Thanks Ed. Is this something that changed from DB2 V8 to V9. It seems to
work fine against our V8 systems.

Jim McAlpine

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
Mentoring should be a rewarding experience for everyone...
IDUG is offering up to 80% off when you both come to the conference!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Edward Long

Re: DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
(in response to Jim McAlpine)
I believe one or more of the defaults changed between 8 and 9.

Edward Long

--- On Tue, 11/16/10, Jim McAlpine <[login to unmask email]> wrote:


From: Jim McAlpine <[login to unmask email]>
Subject: Re: [DB2-L] DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
To: [login to unmask email]
Date: Tuesday, November 16, 2010, 11:57 AM



On Tue, Nov 16, 2010 at 4:42 PM, Ed Long <[login to unmask email]> wrote:






Hi Jim.
There are a set of custom properties that affect the way LOBS get processed by JDBC.
 
To avoid the -4470, and several other user experiences, we have to use the following:
fullyMaterializeLobData=true
fullyMaterializeInputStreams=true
progressiveStreaming=2
progressiveLocators=2
webSphereDefaultIsolationLevel=2
The capitalizations are required. Depending upon whether you use WebSphere, Tomcat or horse and buggy will alter how you define these properties. 

Edward Long

 
Thanks Ed.  Is this something that changed from DB2 V8 to V9.  It seems to work fine against our V8 systems.
 
Jim McAlpine




The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are not already an IDUG member, please register here.

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
Mentoring should be a rewarding experience for everyone...
IDUG is offering up to 80% off when you both come to the conference!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Jim McAlpine

Re: DB2 for z/OS - error accessing DB2 V9 LOB with JCC JDBC driver
(in response to Edward Long)
On Tue, Nov 16, 2010 at 7:30 PM, Ed Long <[login to unmask email]> wrote:

> I believe one or more of the defaults changed between 8 and 9.
>
> Edward Long
>
>
Ed, thanks for the info, that circumvented the problem.

Jim McAlpine

_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv