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

CALLS SQLOGETPERCENTOFAVAILABLEMEMORY DOES NOT REPORT THE FREE MEMORY
CORRECTLY.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Calling a SQL stored procedure with array as input parameter may 
return error 
SQL20442N  There is not enough storage to represent the array 
value. 
SQLSTATE=57011
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.5 on Old Linux level which older than RHEL5           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Calling a SQL stored procedure with array as input           * 
* parametermayreturn errorSQL20442N  There is not enough       * 
* storage to represent thearrayvalue.SQLSTATE=57011            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the OS level to at least RHEL5 as a local fix        * 
****************************************************************
Local Fix:
Upgrade the OS level to at least RHEL5
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Upgrade the OS level to at least RHEL5 as a local fix
Workaround
Upgrade the OS level to at least RHEL5
Comment
Fix Release: V9.5 FP6
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.03.2010
23.06.2010
23.06.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)