DB2 Session Persistence Version 1 failed with a -302 SQL error
 Technote (FAQ)
 
Problem
DB2 session persistence version 1 failed with a -302 SQL error with a J2EE workload running.

DB2JDBCCursor Received Error in Method open:SQLCODE==> -302 SQLSTATE
==> 22001
 
 
Solution
DB2 session persistence version 1 failed with a -302 SQL error with a J2EE workload running. The same workload is running fine with the persistence version 2.

After comparing both the tables, the APPNAME column in the version 1 table is falling short of length of 32, while version 2 has column length of 64.

DB2JDBCCursor Received Error in Method open:SQLCODE==> -302 SQLSTATE
==> 22001

The "Assembling J2EE Applications" manual in Section "2.4.7.3 Configure WebSphere for z/OS to maintain session data in a DB2 database instead of in-memory" talks about the two versions of DB2 session persistence that can be used with WebSphere for z/OS and how you can set his up.


Verify this is setup accordingly to the document where appropriate.

Here is an explanation on the SQL error -302:
Explanation: DB2 received data that was invalid or too large to fit in the corresponding column of the table or the corresponding target value. The position-number identifies either the host variable number (if the message is issued as a result of an INSERT, UPDATE, DELETE, SELECT, VALUES INTO, or SET assignment statement), or the parameter number (if the message is issued as the result of a CALL statement or the invocation of a function).

One of the following occurred:
The column is defined as a string and the host variable or parameter contains a string that is too long for the column.

The column is defined as numeric and the host variable or parameter contains a numeric value too large for the definition of the column.

The host variable is defined as decimal, but contains invalid decimal data.

The target value is a string constant and the host variable or parameter contains a string that is too long for the target value.

The target value is a numeric constant and the host variable or parameter contains a numeric value that is too large for the target value.


System Action: The statement cannot be executed.
Programmer Response: Correct the application program, function or stored procedure. Check the column type and length of the value or the data type and contents of the input host variable or parameter position-number. Ensure that the value of the host variable or parameter will fit in the column or contains valid decimal data. Valid decimal data is a System/370 packed decimal number.

SQLSTATE: 22003 if number too large for target; 22001 otherwise.

The DB2 Messages book states that the -302 error is due to the data being passed
into the DB2 from the application is too large to fit in the corresponding column of the table, APPNAME (32).

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Install
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1105074
IBM Group: Software Group
Modified date: Jan 31, 2005