|
Problem IC88925
|
Status: Closed |
ON LARGE DPF SYSTEMS, DB2START MAY FAIL WITH SQL0901 ON SOME MEMBERS DUE TO INSUFFICIENT FCM MEMORY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* Systems using the DPF feature with a large number of *
* partitions and a high max_coordagents setting *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* reduce the max_coordagents setting to avoid the problem *
**************************************************************** |
| Local Fix: |
Reduce max_coordagents or switch to the AUTOMATIC setting (with
a low underlying value) |
| available fix packs: |
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 first fixed in DB2 Version 10.1 Fix Pack 3 |
| Workaround |
see Local Fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95376
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.12.2012
08.07.2013
08.07.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
