Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC67525 Status: Geschlossen

CALLS SQLOGETPERCENTOFAVAILABLEMEMORY DOES NOT REPORT THE FREE MEMORY
CORRECTLY.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
Upgrade the OS level to at least RHEL5 as a local fix
Workaround
Upgrade the OS level to at least RHEL5
Kommentar
Fix Release: V9.5 FP6
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.03.2010
23.06.2010
23.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version