|
Problem IC66527
|
Status: Closed |
MINOR MEMORY LEAK WHEN USING FEDERATION PASSTHRU FEATURE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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: *
* DB2 Server configured in federation *
****************************************************************
* 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: *
* Recommended to move to V9.5 Fix pack 6. *
**************************************************************** |
| Local Fix: |
Not available. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The issue was fixed in V9.5 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IZ70411 IC66528 IC66696
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.02.2010
17.05.2010
17.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
