|
Problem IC95376
|
Status: Geschlossen |
ON LARGE DPF SYSTEMS, DB2START MAY FAIL WITH SQL0901 ON SOME MEMBERS DUE TO INSUFFICIENT FCM MEMORY |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
A calculation error is causing excessive FCM session memory
usage in DB2 version 10. On DPF systems with a large number of
multiple logical nodes (>= 8) and a large max_coordagents
setting, db2start may fail on some partitions with SQL0901.
db2diag.log entry indicating the problem has occurred:
FUNCTION: DB2 UDB, fast comm manager,
sqkfDynamicResourceMgr::CreateNewResources, probe:50
RETCODE : ZRC=0x8B0F004D=-1961951155=SQLO_NOMEM_FCM_SESSION_HEAP
"No memory available in 'FCM Session Heap'"
DIA8300C A memory heap error has occurred.
error message on db2start:
SQL0901N The SQL statement or command failed because of a
database system error. (Reason "".) |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Large DPF systems *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 3 or apply Local Fix if *
* possible *
**************************************************************** |
| Local-Fix: |
Reduce max_coordagents or switch to the AUTOMATIC setting (with
a low underlying value) |
| verfügbare FixPacks: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
Problem first fixed in DB2 Version 10.5 Fix Pack 3 |
| Workaround |
see Local Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.08.2013
27.02.2014
27.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
