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

MEMORY CORRUPTION DURING LOAD OPERATION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 might crash during processing of the LOAD  and as a 
consequence produce a core file during FODC_Panic execution. 
The symptoms of the problem are corrupted memory with "2020 
2020" footprint during sqluCleanupCLI function call: 
 
2014-12-12-14.12.21.639107-300 I251025E1918        LEVEL: Severe 
PID     : 18979                TID  : 140737115055872 
PROC:db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : DBNAME 
APPHDL  : 1-243                APPID: *N0.db2inst1.1412121912301 
AUTHID  : DBINST1 
EDUID   : 100                  EDUNAME: db2agent (DBNAME) 1 
 
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 0x00007fff5f11f688 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x00007FFF5F11F670 : 2020 2020 0000 0000 0000 0000 0000 0000 
............ 
0x00007FFF5F11F680 : 0000 0000 0000 0000........ 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x00007FFF5F11F688 : 0800 0000 0000 0000 F1B8 4B5F CD01 2F36 
..........K_../6 
0x00007FFF5F11F698 : 10F1 F5FF 0700 B0FA 0000 0000 0000 0000 
................ 
0x00007FFF5F11F6A8 : 10F1 F5FF 0700 B0FA 489F 115F FF7F 0000 
........H.._.... 
 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00007FFFF35CD2DE pdLog + 0x398 
  [1] 0x00007FFFF517942E 
/udb/instance/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x291C42E 
  [2] 0x00007FFFF5EF33B1 sqlofmblkEx + 0x91B 
  [3] 0x00007FFFF5A5D4B2 
_Z18sqluCleanupCLILdCBP20sqlu_loadapi_load_cb + 0x276 
  [4] 0x00007FFFF5A5BA1A _Z18sqluCleanupRemLdCBPP13SQLU_REMLD_CB 
+ 0x1B8 
  [5] 0x00007FFFF5B8B38A 
_ZN24sqlusCLoadMPPCoordinator8iCleanUpEv + 0x470 
  [6] 0x00007FFFF5B8AD95 
_Z28sqlu_register_table_load_MPPP26sqluCLoadRequestDescriptorP15 
sql_static_dataPb + 0x1B9 
  [7] 0x00007FFFF59485A1 _Z17sqluvtld_route_inP12SQLE_DB2RA_T + 
0x71D 
  [8] 0x00007FFFF5A5F32C _Z15sqluTermConnectP14db2UCinterface + 
0x9A 
  [9] 0x00007FFFF377421D sqleUCagentConnectReset + 0xA1 
 
 
The problem had been introduced in DB2 9.7 fixpack 10.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fixpack 11                        * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 version 9.7 fixpack 11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.01.2015
09.10.2015
09.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 FixList