|
Problem IC80070
|
Status: Geschlossen |
MEMORY LEAK HAPPENS ON HADR PRIMARY WHEN HADR IS IN REMOTE CATCHUP STATE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
When HADR primary is in remote catchup state, 64 bytes memory
leak happens each time when db2lfr opens a log file to send to
standby. This could be very serious for HADR with superasync
mode, because HADR is always in remote catchup state with
superasync mode. When hitting this problem, dbheap can increase
very quickly. For example, from output of "db2pd -memb sort 2",
we can see many blocks as follows are left there and increase
quickly.
Memory blocks sorted by size for dbh pool:
PoolID PoolName TotalSize(Bytes) TotalCount LOC File
2 dbh 131703424 2057866 230
1727183880 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* HADR *
****************************************************************
* PROBLEM DESCRIPTION: *
* When HADR primary is in remote catchup state, 64 bytes *
* memory leak happens each time when db2lfr opens a log file *
* to send to standby. This could be very serious for HADR with *
* superasync mode, because HADR is always in remote catchup *
* state with superasync mode. When hitting this problem, *
* dbheap can increase very quickly. For example, from output *
* of "db2pd -memb sort 2", we can see many blocks as follows *
* are left there and increase quickly. *
* *
* Memory blocks sorted by size for dbh pool: *
* PoolID PoolName TotalSize(Bytes) TotalCount LOC *
* File *
* 2 dbh 131703424 2057866 230 *
* 1727183880 *
****************************************************************
* RECOMMENDATION: *
* Update to version 9.5 fixpack 9 or later fixpacks. *
**************************************************************** |
| Local-Fix: |
Use other HADR synchronous modes, eg. ASYNC or NEARSYNC. |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
This problem is first fixed in version 9.5 fixpack 9 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC80105
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 30.11.2011
12.03.2012
12.03.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP9
|
| Problem behoben lt. FixList in der Version |
| 9.5.0.9
|
 |
