DB2 - Problembeschreibung
Problem IC68086 | Status: Geschlossen |
DB2EXT.TEXTSEARCH(FUZZY FORM OF 80 "99????8" CAUSES LARGE AMOUNTS OF MEMORY TO BE ALLOCATED BUT NOT FREED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
NSE query uses up large memory and does not release it even after the application is terminated by db2 force application command. As a result it uses up system memory and new connections fail. Certain NSE searches that uses FUZZY form of option against a large numerical values uses up large amount of memory and fails with CTE0104 or hangs. The issues which need to be fix are: - NSE mallocing large amount of memory - NSE not freeing the memory even when application is terminated from the database. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * NSE query uses up large memory and does not release it even * * * * after the application is terminated by db2 force application * * * * command. As a result it uses up system memory and new * * * * connections fail. * * * * * * * * Certain NSE searches that uses FUZZY form of option against * * a * * large numerical values uses up large amount of * * * * memory and fails with CTE0104 or hangs. * * * * * * * * * * * * The issues which need to be fix are: * * * * * * * * - NSE mallocing large amount of memory * * * * * * * * - NSE not freeing the memory even when application is * * terminated * * from * * * * the database. * **************************************************************** * RECOMMENDATION: * * n/a * **************************************************************** | |
Local-Fix: | |
Lösung | |
Problem is first fixed in Version 9.7 Fix Pack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.04.2010 23.09.2010 23.09.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP3 | |
Problem behoben lt. FixList in der Version |