|
Problem IC97614
|
Status: Closed |
MEMORY LEAKS DURING QUERIES TOUCHING A LARGE NUMBER OF RECENTLY OR CONCURRENTLY UPDATED ROWS ON A COLUMNAR TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
If a columnar table has a large number of recently or
concurrently updated rows, then queries on that table can leak
memory.
For this defect the rows would have to be updated with an UPDATE
statement and INSERT does not count. The actual number depends
on the how the rows were inserted/loaded and which ones were
updated. This can be between half a million and 132 million and
in the latter case it is guaranteed to occur. The leak is
multiples of 4K depending on which areas of the table were
touched and would occur for each query on that table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of column-organized tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.11.2013
16.12.2014
16.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
