home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC88320 Status: Closed

DB2 MAY LEAK DB HEAP EACH TIME LOG IS ARCHIVED UNDER DATABASE THAT HAS
MIRRORLOGPATH BEING SET.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 may leak db heap each time a log is archived when: 
- MIRRORLOGPATH database configuration parameter is set 
 - LOGARCHMETCH1 or LOGARCHMETCH2 is archiving to disk 
 
Leak memory size 2096 ( for DB2 V9.7 )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 2.                   * 
****************************************************************
Local Fix:
Turn off Log Mirroring by setting MIRRORLOGPATH to DEFAULT 
Example: 
db2 update db cfg using MIRRORLOGPATH  DEFAULT
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList