|
Problem IC92227
|
Status: Closed |
MEMORY LEAK IN COMPILER MEMORY POOL WHEN COMPILING A SQL QUERY THAT REFERENCES A FEDERATED DATA SOURCE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When a SQL query that references a federated data source is
compiled, memory might be leaking in the sqlch memory pool. The
size of the leak depends on the number of data sources
referenced, the number of columns in each data source and the
column names. The problem was observed so far only for the DDL
operations on the nicknames.
To check if you hit this APAR, you need to collect a few
iterations of db2pd -memblocks output, and seek for continuously
increasing TotalSize(Bytes) and TotalCount values in following
LOC and File:
PoolID PoolName TotalSize(Bytes) TotalCount LOC
File
50 sqlch 3660006 107738 1028
2675033028
50 sqlch 3680134 108330 1028
2675033028
50 sqlch 3681494 108370 1028
2675033028
...
50 sqlch 4033394 118720 1028
2675033028 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* FEDERATED *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 fix pack 3 *
**************************************************************** |
| Local Fix: |
The leaked memory can be recovered by recycling the DB2 instance |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 version 10.1 fix pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.05.2013
27.09.2013
27.09.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
