DB2 - Problem description
Problem IC80025 | Status: Closed |
REPEATEDLY CALLING A FEDERATED MICROSOFT SQL SERVER STORED PROCEDURE RESULTS INTO PRIVATE MEMORY LEAK. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * USERS AFFECTED: * * all using federated procedure from MS-SQL * **************************************************************** * PROBLEM DESCRIPTION: * * see error description * **************************************************************** * RECOMMENDATION: * * upgrade to version 9.5 fixpack 9 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
first fixed in version 9.5 fixpack 9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC80026 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.11.2011 07.03.2012 07.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |