|
Problem IC95396
|
Status: Geschlossen |
MEMORY LEAK IN COMPILER MEMORY POOL WHEN COMPILING A SQL QUERY THAT REFERENCES A FEDERATED DATA SOURCE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 fix pack 3 *
**************************************************************** |
| Local-Fix: |
The leaked memory can be recovered by recycling the DB2 instance |
| verfügbare FixPacks: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 version 10.5 fix pack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.08.2013
28.02.2014
28.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
