DB2 - Problem description
Problem IC84519 | 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 / A10 - 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 10.1 Fix Pack 1 * **************************************************************** | |
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 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 20.11.2012 20.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |