|
Problem IC88596
|
Status: Closed |
INSTANCE CRASH WITH SIGSEGV OR MEMORY CORRUPTION WHEN RUNNING CLI BASED LOADS, WITH DB2_WORKLOAD=SAP |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When running CLI LOAD operations, there is the potential for
memory corruption which can result a range of symptoms including
a SIGSEGV in runtime (sqlri) or APM (sqlra) related functions.
Some example stacks (but not restricted to these) may look like
the following:
0x090000000BF1ECE8 sqlriSetupStats__FP8sqlrr_cbP9sqlri_shd +
0x320
0x090000000BF1E720 sqlriSectSetup__FP8sqlrr_cbP9sqlri_shd +
0x1B4
0x090000000BC4C784
sqlra_sqlW_get_dynamic_section__FP8sqlrr_cbP16sqlra_cached_var +
0xB88
0x090000000BC4B6BC
sqlra_load_var__FP8sqlrr_cbP16sqlra_cached_var + 0x1B0
0x0900000008BA58E0 sqlriopn__FP8sqlrr_cbP9sqlri_taoPi + 0x37C
0x0900000008BF1208 sqlriopn__FP8sqlrr_cbP9sqlri_taoPi@glue270 +
0x90
0x0900000008BF10DC sqlrita__FP8sqlrr_cb + 0x54
0x0900000008BF5544 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x28
0x0900000007393CEC
sqlra_sqlW_get_dynamic_section__FP8sqlrr_cbP16sqlra_cached_var +
0x650
0x090000000AD576BC
sqlra_load_var__FP8sqlrr_cbP16sqlra_cached_var + 0x1B0
0x090000000AD57318 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0xA04
0x09000000072E31DC sqlofmblkEx + 0x124
0x09000000065637AC sqlyt_trf_dealloc__FPP14sqlyt_trf_grps +
0x1B0
0x09000000090BC7FC sqlristm__FP8sqlrr_cbP9sqlri_shdi + 0x140
0x09000000073B46D0
sqlra_sqlW_mem_free_sibling_list__FP8sqlrr_cbP23sqlra_workspace_
siblingPUl + 0x3D8
0x0900000007657B44
sqlra_sqlW_mem_free_variation_siblings_new__FP8sqlrr_cbP16sqlra_
cached_var + 0x544
In some cases, this APAR may also result in a panic and
instance shutdown due to detected memory corruption
(sqloCrashOnCriticalMemoryValidationFailure).
This APAR is ONLY applicable when the registry variable
DB2_WORKLOAD is set to SAP AND if there is a code page
conversion i.e. Input data code page is different than the
database code page. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 version 10.1 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2012
09.01.2013
22.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
