DB2 - Problembeschreibung
Problem IC67521 | Status: Geschlossen |
SCAN SHARING FOR MDC BLOCK INDEX SCAN CAUSES MEMORY LEAK ON DBHEAP. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problembeschreibung: | |
The database heap might keep growing like as below: Memory for database: SAMPLE utilh pckcacheh other catcacheh bph (6) bph (5) 192.0K 51.1M 192.0K 2.1M 158.1M 398.9M bph (4) bph (3) bph (2) bph (1) bph (S32K) bph (S16K) 203.6M 315.9M 1.6G 610.4M 832.0K 576.0K bph (S8K) bph (S4K) shsorth lockh dbh apph (29148) 448.0K 384.0K 2.1M 44.0M 18.3G 64.0K 'db2pd -db <dbname> -memb' command shows number of specific memory blocks keep growing, and the blocks share major part of dbheap. Please look LOC (700) and File (1232204724) to identify this problem. PoolID PoolName TotalSize(Bytes) TotalCount LOC File 2 dbh 883638912 531033 700 1232204724 The memory blocks are allocated by scan sharing functionality to hold a key of block index scan. DB2 has a code path which does not free the memory blocks even if the database retains no scan sharing sets. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users who use IXSCAN for MDC block indexes. * **************************************************************** * PROBLEM DESCRIPTION: * * The database heap might keep growing like as below: * * * * Memory for database: SAMPLE * * * * utilh pckcacheh other catcacheh bph (6) bph (5) * * 192.0K 51.1M 192.0K 2.1M 158.1M 398.9M * * * * bph (4) bph (3) bph (2) bph (1) bph (S32K) bph * * (S16K) * * 203.6M 315.9M 1.6G 610.4M 832.0K 576.0K * * * * bph (S8K) bph (S4K) shsorth lockh dbh apph * * 448.0K 384.0K 2.1M 44.0M 18.3G 64.0K * * * * 'db2pd -db <dbname> -memb' command shows number of specific * * memory blocks keep growing, and the blocks share major part * * of dbheap. * * Please look LOC (700) and File (1232204724) to identify this * * problem. * * PoolID PoolName TotalSize TotalCount LOC File * * 2 dbh 883638912 531033 700 1232204724 * * * * The memory blocks are allocated by scan sharing * * functionality to hold a key of block index scan. DB2 has a * * code path which does not free the memory blocks even if the * * database retains no scan sharing sets. * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V9.8 fixpack 3 or later. * **************************************************************** | |
Local-Fix: | |
Users can disable scan sharing by using optimizer profiles. | |
verfügbare FixPacks: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.8 Fix Pack 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 29.03.2010 21.12.2010 21.12.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.8.FP3 | |
Problem behoben lt. FixList in der Version | |
9.8.0.3 |