DB2 - Problem description
Problem IT04587 | Status: Closed |
POSSIBLE MEMORY CORRUPTION DETECTED MESSAGE REPORTED IN SQLUDMSORTFREEINXCB WHEN PERFORMING A CURSOR LOAD. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When we have CPU_PARALLELISM set to a value greater than 27 explicitly or implicitly, the instance might crash with a possible memory corruption detected message in db2diag.log when performing a cursor load. db2diag.log will have entries similar to the following 2014-09-17-04.00.01.948960-240 I20911E529 LEVEL: Warning PID : 2710744 TID : 140334889690880PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TESTDB APPHDL : 0-83 APPID: *LOCAL.db2inst1.140917075957 AUTHID : db2inst1 EDUID : 198 EDUNAME: db2lrid FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:314 DATA #1 : String, 100 bytes LOADID: 16.2014-09-17-03.59.38.013429.0 (3;4) Completed BUILD phase at 17-09-2014 04:00:01.948908. 2014-09-17-04.00.02.049135-240 I21441E1776 LEVEL: Severe PID : 2710744 TID : 140334889690880PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TESTDB APPHDL : 0-83 APPID: *LOCAL.db2inst1.140917075957 AUTHID : db2inst1 EDUID : 198 EDUNAME: db2lrid FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:10 MESSAGE : Possible memory corruption detected. DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 0x820F0002 DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 bytes 0x00007fa30221f220 DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 0x00007FA30221F208 : E0AF 0200 817F 0000 0000 001D 5D0A 8610 ............]... 0x00007FA30221F218 : 1022 30FA 0100 802C ."0...., DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 0x00007FA30221F220 : 0000 0000 0000 0300 0000 0000 0000 0000 ................ 0x00007FA30221F230 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00007FA30221F240 : 0000 0100 0400 0200 C0FE 6501 A37F 0000 ..........e..... CALLSTCK: [0] 0x00007FA4B7B82F52 pdLog + 0x398 [1] 0x00007FA4B9667FDC /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x2823FDC [2] 0x00007FA4BA3AA5F3 sqlofmblkEx + 0x8F3 [3] 0x00007FA4B9EDB308 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x3097308 [4] 0x00007FA4B9EDB4A5 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x30974A5 [5] 0x00007FA4B9EDBB39 _Z19sqluDMSortTerminatePPh + 0xD7 [6] 0x00007FA4B9EA6E32 _Z21sqluTerminateLoadSortP13SQLUCACB_TYPEP18SQU_EDU_ESSENTIALS + 0x84 [7] 0x00007FA4B9ED40F7 /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x30900F7 [8] 0x00007FA4B9ED3D4B _ZN11sqluCRidder8iCleanUpEi + 0x145 [9] 0x00007FA4B9ED742B _Z17sqluLoadEDUDriverPhj + 0x36F This APAR will resolve the above observed issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 for LUW Version 9.7 FixPack 11 or higher. * **************************************************************** | |
Local Fix: | |
set CPU_PARALLELISM to a value lower than 27. | |
Solution | |
Firstly fixed in DB2 for LUW Version 9.7 FixPack 11. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.09.2014 13.10.2015 13.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.11 |