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 IC76040 Status: Closed

PARAMETER NUMBER IS NOT DISPLAYED FOR ERRORS -301 AND -311 WHEN ERROR IS
COMING FROM DB2/Z

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Error messages -301 and -311 coming from DB2/z server do not 
show parameter number: 
 
SQL0301N  The value of input variable, expression or parameter 
number "" cannot be used because of its data type. 
SQLSTATE=42895 
 
SQL0311N The length of string host variable number "" is 
negative or greater than the maximum. SQLSTATE=22501
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users working with DB2/z databases                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Error messages -301 and -311 coming from DB2/z server do not * 
* show parameter number:                                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL0301N  The value of input variable, expression or         * 
* parameter number "" cannot be used because of its data type. * 
* SQLSTATE=42895                                               * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL0311N The length of string host variable number "" is     * 
* negative or greater than the maximum. SQLSTATE=22501         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
The problem is first fixed in DB2 Version 9.7 Fix Pack 5 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.04.2011
07.12.2011
07.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.