|
Problem IT23421
|
Status: Closed |
ONCE SQL0954C IS FACED WITH APPLHEAPSZ DURING DB UPGRADE MAKE THE PARAMETER AUTO INTERNALLY FOR THE UPGRADE DURATION.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In times a db2 upgrade might face SQL0954C with APPLHEAPSZ if
the parameter has a fixed insufficient size.
2017-11-19-08.56.34.615771-300 I227079A782 LEVEL: Event
PID : 26476900 TID : 4884 PROC :
db2sysc 0
INSTANCE: udbinst1 NODE : 000 DB :
APPHDL : 0-59 APPID:
AUTHID : HOSTNAME:
EDUID : 4884 EDUNAME: db2agent () 0
FUNCTION: DB2 UDB, catalog migration,
sqlrlm_catalog_parallel_migrate, probe:7236
MESSAGE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH
"No memory available in 'Application Heap'"
DIA8301C No memory available in the application heap.
DATA #1 : String, 35 bytes
Terminating parallel upgrade worker
DATA #2 : unsigned integer, 8 bytes
0
DATA #3 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-954
This defect fix will change the APPLHEAPSZ parameter internally
to AUTOMATIC and change it back at the end of the upgrade steps. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Upgrade *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* This APAR was created to make the upgrade step more *
* intelligent internally by modifying the application heap, *
* if it's missed by the end user. *
* But, found out to be not possible to implement as part of *
* APAR fix. So, there will be no fixes put against this. *
* *
* Make sure the APPLHEAPSZ is sufficiently configured or, set *
* it to AUTOMATIC before the upgrade try. That will avoid the *
* issue. *
**************************************************************** |
| Local Fix: |
Change with APPLHEAPSZ to AUTOMATIC |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.12.2017
17.12.2018
17.12.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
