suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT26072 Status: Closed

UPGRADE DATABASE COMMAND RETURNS SQL1224, SQL0954 WHEN APPLHEAPSZ IS SET
TO SMALL FIXED VALUE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When the application heap size is set to a small fixed value,
the limit may be encountered causing the upgrade database
command to fail. The error should be SQL0954, but in some cases
the error condition is not handled correctly, resulting in a
panic/abend (SQL1224).

The APAR will correct the error handling code as well as add a
temporary APPLHEAPSZ setting override during the database
migration process (to the default setting of
unlimited/AUTOMATIC).

First symptom in the db2diag.log will be an OOM (out of memory),
eg.:
FUNCTION: DB2 UDB, SQO Memory Management,
sqloMemLogPoolConditions, probe:30
DATA #1 : 
Out of memory failure for Application Heap (APPLHEAPSZ) on node
0.

Other messages may follow, and the instance may abend/panic.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Database migrations with small fixed APPLHEAPSZ setting      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Use Local Fix                                                *
****************************************************************
Local Fix:
update the APPLHEAPSZ setting to the default (AUTOMATIC) and
reissue the UPGRADE DATABASE command
Solution
Workaround
Use Local Fix
Comment
Use Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.08.2018
11.07.2019
11.07.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)