DB2 - Problem description
Problem IC73240 | Status: Closed |
MEMORY LEAK IN THE PRIVATE MEMORY SET ON HADR STANDBY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Memory can be leaked when moving an extent during the redo/undo operation. This causes the private memory set to grow. This leak is most likely to be noticed on an HADR standby database and will manifest as a hang situation when primary is blocked from committing due to poor performance of standby. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users with a large amount of undo/redo processing * **************************************************************** * PROBLEM DESCRIPTION: * * Memory can be leaked when moving an extent during the * * redo/undo operation. This causes the private memory set to * * grow. This leak is most likely to be noticed on an HADR * * standby database and will manifest as a hang situation when * * primary is blocked from committing due to poor performance * * on the standby. * * * * Symptoms of this issue: * * * All memory on the machine is consumed * * * The PRIVATE memory set (db2pd -dbptnmem) is unexpectedly * * large * * * Redo processing on the standby will be very slow due to * * the shortage of memory * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 FP4 or newer. * **************************************************************** | |
Local Fix: | |
Stopping and starting HADR on the primary has been seen to release this memory. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 v9.7 FP4 or newer. | |
Workaround | |
Stopping and starting HADR on the primary has been seen to release this memory. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.12.2010 09.05.2011 09.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |