home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC81838 Status: Closed

CLI/.NET APPLICATIONS FAIL WITH SQL30020N/SQL30081N WHEN EXECUTI NG A
STORED PROCEDURE WITH A RETURN VALUE, AND LOB IN PARAMETER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If a stored procedure has a return value and LOB IN parameter 
that requires streaming the LOB data, then executing the 
procedure can fail with one of the following messages: 
 
SQL30020N  Execution of the 
command or SQL statement failed because of a syntax error in the 
communication data stream that will affect the successful 
execution of subsequent commands and SQL statements:  Reason 
Code "0x124C"("020A")"".  SQLSTATE=58009 
 
or 
 
SQL30081N  A communication error has been detected. 
Communication protocol being used: "TCP/IP".  Communication API 
being used: "SOCKETS".  Location where the error was detected: 
"141.128.71.208".  Communication function detecting the 
error:"recv".  Protocol specific error code(s): "*", "*", "0". 
SQLSTATE=08001 
 
This can occur in one of the following cases: 
 
- A .NET application that uses 
DB2CommandBuilder.DeriveParameters() 
OR 
-  A CLI application that has CALL statement with explicit 
parameter for return value of the form "{?=call proc(?)}".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CLI/.NET APPLICATIONS FAIL WITH SQL30020N/SQL30081N WHEN     * 
* EXECUTI                                                      * 
* NG A STORED PROCEDURE WITH A RETURN VALUE, AND LOB IN        * 
* PARAMETER                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6                        * 
****************************************************************
Local Fix:
As a work-around explicitly set the LOB parameter size to 0 in 
.NET applications. 
 
For example the sample code would look like: 
 
                cmd.Parameters["IN_LOB_PARAM"].Size = 0; 
//IN_LOB_PARAM is LOB IN parameter
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84519 IC88221 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.03.2012
14.11.2012
14.11.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList