DB2 - Problem description
Problem IC66696 | Status: Closed |
MINOR MEMORY LEAK WHEN USING FEDERATION PASSTHRU FEATURE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
When user runs some query in passthru session like this set passthru server1; select * from sometable; set passthru reset; and then dump the DB2 memory blocks using db2pd like "db2pd -memblock", they can see some leaked memory blocks like below: Address PoolID PoolName BlockAge Size(Bytes) I LOC File 0x0000000110E7EB88 88 private 445 16 1 451 2074526459 0x0000000110E7EBC8 88 private 452 16 1 451 2074526459 0x0000000110E7ECA8 88 private 450 144 1 451 2074526459 0x0000000110E7ED68 88 private 451 144 1 451 2074526459 0x0000000110E7EEA8 88 private 457 144 1 451 2074526459 0x0000000110E7EF68 88 private 458 144 1 451 2074526459 0x0000000110E7F0A8 88 private 461 144 1 451 2074526459 0x0000000110E7F168 88 private 462 144 1 451 2074526459 In databases with health monitor enabled and Federated datasource servers defined, this issue manifests itself even though user doesn't run explicitly and passthru commands. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User using passthru session in DPF environment. * **************************************************************** * PROBLEM DESCRIPTION: * * When user runs some query in passthru session like this * * * * set passthru server1; * * * * select * from sometable; * * * * set passthru reset; * * * * * * * * and then dump the DB2 memory blocks using db2pd like "db2pd * * * * -memblock", they can see some leaked memory blocks like * * below: * * * * * * Address PoolID PoolName BlockAge Size(Bytes) I * * LOC File * * * * 0x0000000110E7EB88 88 private 445 16 1 * * 451 2074526459 * * * * 0x0000000110E7EBC8 88 private 452 16 1 * * 451 2074526459 * * * * 0x0000000110E7ECA8 88 private 450 144 * * 1 * * 451 2074526459 * * * * 0x0000000110E7ED68 88 private 451 144 * * 1 * * 451 2074526459 * * * * 0x0000000110E7EEA8 88 private 457 144 * * 1 * * 451 2074526459 * * * * 0x0000000110E7EF68 88 private 458 144 * * 1 * * 451 2074526459 * * * * 0x0000000110E7F0A8 88 private 461 144 * * 1 * * 451 2074526459 * * * * 0x0000000110E7F168 88 private 462 144 * * 1 * * 451 2074526459 * * * * * * * * In databases with health monitor enabled and Federated * * * * datasource servers defined, this issue manifests itself even * * * * though user doesn't run explicitly and passthru commands. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.8 Fix pack 3. * **************************************************************** | |
Local Fix: | |
Not available. | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.8 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.02.2010 21.12.2010 21.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |