DB2 - Problem description
Problem IC91767 | Status: Closed |
AN OUT OF MEMORY ERROR ENCOUNTERED WHILST COPYING A DATA DESCRIPTOR COULD LEAD TO A CRASH. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If a memory allocation error occurs whilst a data descriptor, an internal structure used for data encapsulation within DB2, is being copied it is possible that uninitialised content is picked up and used when the partial copy is freed, leading to a crash. As the uninitialised data will vary, exact symptoms of the crash will vary too however the faulting stack should contain the function sqlofmblkEx called by sqlddFreeDD, for example: =========================================== [0] 0x090000000631D6B8 pdLog + 0x88 [1] 0x09000000074466AC @78@sqloDiagnoseFreeBlockFailure__... + 0xEC [2] 0x09000000074464F0 sqloDiagnoseFreeBlockFailure__... + 0x78 > [3] 0x09000000060CFBF8 sqlofmblkEx + 0x80 > [4] 0x09000000062F123C sqlddFreeDD__FPP14dataDescriptor + 0x9C [5] 0x0900000006D08060 sqluFreeCrossCBMemory__... + 0x2B4 [6] 0x0900000006D06F2C iCleanUp__... + 0x520 [...] =========================================== This APAR will ensure data descriptor memory is correctly initialised when allocated. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of version 10.1 on Linux, Unix and Windows * * platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to DB2 LUW Version 10.1 Fix Pack 3 or higher levels. * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 LUW Version 10.1 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 31.10.2013 31.10.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 |