|
Problem IT01986
|
Status: Closed |
MEMORY LEAK HAPPENS WHEN FEDERATED SET TO 'Y' |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If the db2 dbm config has the FEDERATED parameter set to 'Y',
then there is memory leak for any query with or without
federated server nicknames.
The problem exists in DB2 v10.1 and any after that.
The memory leak could be reproduced by using following steps
where the FEDERATED dbm config parameter is set to YES and a
query is issued with a non-existent table.
$ db2 get dbm cfg | grep FEDERATED
Federated Database System Support (FEDERATED) = YES
$ db2 select * from blah
SQL0204N "XXX.BLAH" is an undefined name. SQLSTATE=42704
$ db2pd -memblocks pid=`db2pd -edus|awk '/db2sysc PID/ {print
$NF}'` sort|egrep "sqlqg_misc.C|sqlqg_catalog.C"
0 984 9 451
sqlqg_misc.C
0 249 21 1874
sqlqg_catalog.C
$ db2 select \* from blah
SQL0204N "XXX.BLAH" is an undefined name. SQLSTATE=42704
$ db2pd -memblocks pid=`db2pd -edus|awk '/db2sysc PID/ {print
$NF}'` sort|egrep "sqlqg_misc.C|sqlqg_catalog.C"
0 1312 12 451
sqlqg_misc.C
0 308 28 1874
sqlqg_catalog.C |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using FEDERATED=YES *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Users can upgrade to DB2 Version 10.1 fix pack 5 or higher *
* to avoid this defect *
**************************************************************** |
| Local Fix: |
Set the dbm config parameter FEDERATED=NO |
| Solution |
First fixed in DB2 Version 10.1 fix pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.05.2014
12.08.2015
12.08.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
