PQ60115: GET "SQL0302N THE VALUE OF A HOST VARIABLE IN THE EXECUTE OR STATEMENT IS TOO LARGE" WHEN PERSISTING SESSION TO DB2/OS390 | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Using DB2/OS390 as session persistent database, occasionally get the exception: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2] SQL0302N The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. SQLSTATE=22001 . The reason why the code doesn't work when persisting session data to DB2/OS390 is: The following call is being made to retrieve column metadata, does not return any data when using DB2/OS390 (it works fine with DB2 UDB): getColumns(null, null, "WEBSPHR.SESSIONS", "%") . The following code works on both DB2 UDB and DB2/OS390: getColumns(null, null, "SESSIONS", "%") or if the schema name is needed, then use the following call: getColumns(null,"SCHEMA_NAME","TABLE_NAME","%");Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server Session Manager * * Users * **************************************************************** * PROBLEM DESCRIPTION: Sessions Persistence was failing when * * the session object's size was between * * 29K and 32K. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the Distributed environment the medium column in the sessions table gets created with a size of approximately 32K. In the DB2/390 environment the medium column gets created with a size of approximately 29K. So whenever the size of the session object was between 29K and 32K, session persistence was failing. Now the session manager uses the correct size of the medium column in its database manipulations.Problem conclusion This problem was originally reported in PQ57776, but the original problem was not corrected in that APAR. The session tracking code was changed to fix this problem.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ60115
IBM Group: Software Group
Modified date: Jun 27, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.