|
Problem IC92001
|
Status: Closed |
MEMORY CORRUPTION ISSUE WITH XML ON DPF ENV |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When large XML data (more then 128K) is used in host variables
on DPF , then it is possible to hit memory corruption issue.
The memory corruption will have a signature such as below in the
mem_diagnostics file dump:
-- UNKNOWN NODE TYPE --
00002aaace6a5d08 : 00 00 10 00 00 00 11 00 00 00 12 00 00 00 13
00 ................
00002aaace6a5d18 : 00 00 14 00 00 00 15 00 00 00 16 00 00 00 17
00 ................
================================================================
=============
Stack that can result form this memory corruption is:
sqloCrashOnCriticalMemoryValidationFailure
diagnoseMemoryCorruptionAndCrash
MemTreePut
sqlofmblkEx
sqlristm
sqlra_sqlW_mem_free_sibling_list
sqlra_sqlW_mem_freespace
sqlra_sqlW_check_for_cleanup
sqlra_sqlW_get_dynamic_section
sqlra_load_var
sqlra_get_var
sqlrr_prepare |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* MEMORY CORRUPTION ISSUE WITH XML ON DPF ENV *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* First Fixed in fix pack 3 of DB2 v10.1 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in fix pack 3 of DB2 v10.1 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95291
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.04.2013
07.10.2013
07.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
|
|
