|
Problem IT40351
|
Status: Closed |
SEVERITY CHANGE OF LOG ENTRY: "FUNCTION: DB2 UDB, ROUTINE_INFRASTRUCTURE, SQLERINITFMPHEAP, PROBE:995* RETCODE : ZRC=0X00000000=
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Customer complains that it is not normal to issue first a Severe
error that FMP HEAP could not be initialized then issue a
warning that zone is setup to 0.
Customer expects following fix on this
The DB2 code is :
first trying to initialize the zone ==> Severe: "I cannot
allocate"
issue a warning " ah yes, the zone is 0"
This behavior triggers alerts for CU because they parse Severe
errors, so the correct DB2 code should be:
issues a warning "the zone is 0"
Do not try to allocate as it is 0
For this case(DB2_FMP_COMM_HEAPSZ is set to 0) we don't need to
log the message in sqlerInitFmpHeap as severe (Change: LEVEL:
Severe to LEVEL: Warning) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* SP users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.8.0 or higher. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* SP users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.8.0 or higher. *
**************************************************************** |
| Comment |
See Error Description.
This issue was fixed in 11.5.8 or higher. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.03.2022
16.05.2022
16.05.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
