home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC80026 Status: Geschlossen

REPEATEDLY CALLING A FEDERATED MICROSOFT SQL SERVER STORED PROCEDURE
RESULTS INTO PRIVATE MEMORY LEAK.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
PRIVATE memory leak may occur when calling a federated procedure 
on SQL Server. The PRIVATE memory will increase up until the 
instance is recycled. This issue affects only calls to stored 
procedures via a Microsoft SQL Server wrapper.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All using federated stored procedures on MS-SQL              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to version 9.7 fixpack 6                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
first fixed in version 9.7 fixpack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.11.2011
04.06.2012
04.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList