suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT39973 Status: Closed

Frequent activation/deactivation can cause file handle leak and increase
in memory on db2 server

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
This problem only affects Windows platform.

Some memory were not freed on database deactivate,
increasing the memory usage on Windows over time and
leads to out of memory issue.

The following shows an example of how this problem can
affect the memory usage on Windows.

Memory usage from db2 command output looks normal.

db2pd -mem output:
Database Member Memory Controller Statistics
Memory Limit:     29564116 KB
Current usage:    2923776 KB   --> 2.78gb

db2pd -winx output:
Total is 35208964    ?> 33.577gb
Others : 25801340  ?> 24.60gb
db2 - 9407624        ?> 8.97gb
db2fmp - 6063872  ?> 5.78gb

However Windows tasklist shows much more and continues to rise
over time:
db2syscs.exe         2560 Services          0 47,408,100 K. ??>
45.21 gb


Because the problem is only triggered when the database is
deactivated, it can be avoided by explicitly activate the
database via the ACTIVATE DATABASE command.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Windows                                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 v11.5.8.0                                     *
****************************************************************
Local Fix:
Explicitly activate the database via the ACTIVATE DATABASE
command.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Windows                                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 v11.5.8.0                                     *
****************************************************************
Comment
Fix in Db2 v11.5.8.0.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.02.2022
27.04.2022
27.04.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)