DB2 - Problem description
Problem IT15213 | Status: Closed |
LOAD TABLE WITH LOB IN DPF PARTITIONED TABLE MIGHT CORRUPT MEMORY | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The conditions for this to happen are: - The table must contain at least one LOB column. - The table must be partitioned in DPF system. The memory corruption can create all sorts of traps but here are some found for this case: 0x00007F865C0DFB60 SQLO_MEM_POOL::MemTreePut + 0x0260 0x00007F865C0DB845 sqlofmblkEx + 0x0225 0x00007F8659B67B9D sqlo_recycle_EDU_data + 0x007d 0x00007F8659B6B2E2 sqloRemoveEDUResources + 0x01a2 0x00007F8659B6B023 sqloExitEDU + 0x0113 0x00007F865907AF10 sqeAgent::recycleAgent + 0x00f0 0x00007F8659078BBB sqeAgent::RunEDU + 0x033b 0x00007F865A0FDE63 sqzEDUObj::EDUDriver + 0x00f3 0x00007F865A0FDD69 sqlzRunEDU + 0x0009 0x00007FF1FA0F2C40 sqloCrashOnCriticalMemoryValidationFailure + 0x0020 0x00007FF1FAF3BB3B sqlofmblkEx + 0x051b 0x00007FF1FAADCDEF sqlusCDataBuffer::iCleanUpEv + 0x001f 0x00007FF1FAADEEA7 sqlusCRawUserDataBuffer::iCleanUpEv + 0x0047 0x00007FF1FAAF11FE sqlusCRawCrossBuffer::iCleanUpEv + 0x002e 0x00007FF1FAAC7053 sqlusCLoadMPPCoordinator::iCleanUpEv + 0x02b3 0x00007FF1FAAC5797 sqlu_register_table_load_MPP + 0x01a7 0x00007FF1F8DBAC11 sqluvtld_route_in + 0x0b61 0x00007FF1F7EB67DD sqlesrvr + 0x01ed 0x00007FF1F7ED5273 sqleMappingFnServer + 0x04c3 The corrupted memory would show the following pattern: 0x00007FF1A566EFE0 0000000001000000 0200000003000000 ................ 0x00007FF1A566EFF0 0300000003000000 0300000003000000 ................ 0x00007FF1A566F000 0300000003000000 0300000003000000 ................ 0x00007FF1A566F010 0300000004000000 0400000004000000 ................ 0x00007FF1A566F020 0500000005000000 0600000007000000 ................ 0x00007FF1A566F030 0800000008000000 0800000008000000 ................ 0x00007FF1A566F040 0900000009000000 0A0000000A000000 ................ 0x00007FF1A566F050 0B0000000C000000 0D0000000D000000 ................ ... towards the end of block and next blocks ... 0x00007FF1A568FFA0 C9010000C9010000 CA010000CA010000 ................ 0x00007FF1A568FFB0 CB010000CC010000 CC010000CC010000 ................ 0x00007FF1A568FFC0 CD010000CE010000 CE010000CE010000 ................ 0x00007FF1A568FFD0 CF010000D0010000 D1010000D2010000 ................ 0x00007FF1A568FFE0 D2010000D2010000 D3010000D4010000 ................ 0x00007FF1A568FFF0 D5010000D6010000 D6010000D7010000 ................ 0x00007FF1A5690000 D8010000D9010000 DA010000DB010000 ................ 0x00007FF1A5690010 DC010000DD010000 DE010000DF010000 ................  | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 8 * **************************************************************** | |
Local Fix: | |
Attempt a load with smaller number of rows.  | |
Solution | |
First fixed in DB2 10.5 Fix Pack 8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.05.2016 13.03.2017 13.03.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |