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 IT28414 Status: Closed

DB2 MIGHT CRASH IN SQLOFMBLKEX->SQLO_MEM_POOL::MEMTREEPUT WITH "CORRUPT
POOL FREE TREE NODE" ERROR MESSAGE IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Db2 might crash when freeing memory of certain sizes. Trap file
& db2diag.log will show the following functions on the top of
the stack:

SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
SQLO_MEM_POOL::MemTreePut
sqlofmblkEx

and an error message reported to db2diag.log will indicate a
corrupt pool free tree:

FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:999
MESSAGE : Memory validation failure, diagnostic file dumped.
DATA #1 : String, 28 bytes
Corrupt pool free tree node.

Problem is specific to Db2 11.1 Mod 4 FP4 (also iFix 001)
environments and is more likely to happen if DB_MEM_THRESH is
*not* set to 100 (which is the recommended value). One of the
code paths affected is backup - at the end of backup instance
might crash with the following functions on the top of the
stack:

SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash
SQLO_MEM_POOL::MemTreePut
sqlofmblkEx
sqluxFreeAllMem
sqlubcka
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All users                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 11.1 Mod 4 Fix pack 5                 *
****************************************************************
Local Fix:
Verify DB_MEM_THRESH for the database and set it to 100 if the
current value is different, which should greatly reduce the risk
of hitting the error.

For BACKUP scenarios, use a different size backup buffer e.g. 2
buffers more (or less) than the current value, which triggered
the crash.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : 424AC6Ÿ IT30792 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2019
10.07.2019
10.07.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)