home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC85501 Status: Geschlossen

INSTANCE CRASH WITH SIGSEGV OR MEMORY CORRUPTION WHEN RUNNING CLI BASED
LOADS, WITH DB2_WORKLOAD=SAP

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users with SAP workload and code page conversion.            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgade to DB2 Version 9.7 Fix Pack 7                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 Version 9.7 Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC88596 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.07.2012
15.11.2012
22.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList