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 IC85725 Status: Geschlossen

SIGNAL 11 IN SQLSFETC AFTER MEMORY ALLOCATION ERROR IN SQLSBINSORTALLOCMEM

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
An error during a retry of a memory allocation failure can lead 
to a signal 11. 
 
2012-06-29-16.22.20.224214-240 I345305072A3808      LEVEL: 
Warning 
PID     : 28246218             TID : 7970           KTID : 
40763441 
PROC    : db2sysc 
INSTANCE: jabrum2              NODE : 000           DB   : SQEEI 
APPHDL  : 0-802                APPID: 
*LOCAL.jabrum2.120629202728 
AUTHID  : JABRUM2              HOSTNAME: pscalep74008a 
EDUID   : 7970                 EDUNAME: db2agent (SQEEI) 
FUNCTION: DB2 UDB, SQO Memory Management, sqlogmblkEx, 
probe:1000 
MESSAGE : ZRC=0x8B0F0012=-1961951214=SQLO_NOMEM_SHARED_SORT 
          "No memory available in 'Shared Sort Heap'" 
          DIA8300C A memory heap error has occurred. 
DATA #1 : String, 43 bytes 
Memory management block allocation failure. 
DATA #2 : Codepath, 8 bytes 
0 
DATA #3 : Memory pool handle pointer, 
PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes 
0x070000010dc201a8 
DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes 
81880 
DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8 
bytes 
0 
DATA #6 : Options for requested block, PD_TYPE_GET_MEM_OPTIONS, 
4 bytes 
0x00000000 
DATA #7 : Pointer to address that will be set by new allocation, 
PD_TYPE_PTR_TO_ADDRESS_OUT, 8 bytes 
0x070000010dd003c8 
DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 11 bytes 
sqlsbsort.C 
DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes 
2438 
DATA #10: Resource binding pointer, 
PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes 
0x0000000000000000 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x09000000318CEE30 pdLog + 0x290 
  [1] 0x09000000318890D4 sqlogmblkEx + 0x1C74 
  [2] 0x0900000034537CE0 
sqlsBinSortAllocMem__FP10SQLS_SLDESP10SQLS_SORTSUlPiPUl + 0x3E0 
  [3] 0x09000000345385E8 
sqlsBinSortIncremental__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSi + 
0x348 
  [4] 0x090000003734A460 
sqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQLD_CCBPcPUcP12sqlri_ 
vectorPP10SQLD_VALUE + 0x9E0 
  [5] 0x090000003974F39C 
sqlrsopen__FP8sqlrr_cbP9sqlri_taoiT3P10sqlri_iudo + 0x1BC 
  [6] 0x0900000039781D48 sqlrisrt__FP8sqlrr_cb + 0x528 
  [7] 0x090000003976A828 
sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 0x5A8 
  [8] 0x090000003977B7B8 
sqlri_handle_slowtemp__FP8sqlrr_cbP9sqlri_taoP10sqlri_evlo + 
0xF8 
  [9] 0x090000003977C964 sqlrita__FP8sqlrr_cb + 0x724 
  [10] 0x0900000039E2CDE8 
sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 0x5A8 
  [11] 0x0900000039E2D27C sqlriunn__FP8sqlrr_cbP10sqlri_stob + 
0x1BC 
  [12] 0x0900000039E2D874 sqlriset__FP8sqlrr_cb + 0x1F4 
 
 
The associated stack traceback: 
Signal #11 (SIGSEGV): si_addr is 0x0000000000000000, si_code is 
0x00000001 (SEGV_MAPERR:Address not mapped to object.) 
 
0x00002AAAB2445F1A 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x020a 
    (/home/hotel61/leechu/sqllib/lib64/libdb2osse.so.1) 
0x00002AAAB2445CAB ossDumpStackTraceV98 + 0x002b 
    (/home/hotel61/leechu/sqllib/lib64/libdb2osse.so.1) 
0x00002AAAB2440BD3 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x0103 
    (/home/hotel61/leechu/sqllib/lib64/libdb2osse.so.1) 
0x00002AAAAE042FB7 sqlo_trce + 0x0407 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAE08D637 sqloEDUCodeTrapHandler + 0x0277 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAABD4D60 address: 0x00002AAAAABD4D60 ; dladdress: 
0x00002AAAAABC7000 ; offset in lib: 0x000000000000DD60 ; 
    (/lib64/libpthread.so.0) 
0x00002AAAAEF2F252 
_Z8sqlsfetcP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL 
Z_RIDPc + 0x0af2 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAEF07CA3 _Z10sqlriFetchP8sqlrr_cbP9sqlri_taol + 0x0183 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAACBBF1FA 
_Z21sqlri_handle_slowtempP8sqlrr_cbP9sqlri_taoP10sqlri_evlo + 
0x007a 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAEF171FD _Z7sqlritaP8sqlrr_cb + 0x05dd 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAACB8CF5D _Z15sqlriExecThreadP8sqlrr_cbP12sqlri_opparm 
+ 0x007d 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAACBB69EA _Z8sqlriunnP8sqlrr_cbP10sqlri_stob + 0x00aa 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAACBB6625 _Z8sqlrisetP8sqlrr_cb + 0x06f5 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAACBB084F _Z8sqlrievlP8sqlrr_cb + 0x012f 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAEF0A89D _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x01ad 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1) 
0x00002AAAACA84805 
_Z27sqlrr_process_fetch_requestP14db2UCinterface + 0x01b5 
    (/home/hotel61/leechu/sqllib/lib64/libdb2e.so.1)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 configurations.                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp2.                                      * 
****************************************************************
Local-Fix:
Disabling binsort is a workaround but may reduce sorting 
performance.  Applying the fixpack is the recommended course of 
action. 
 
db2set DB2_BINSORT=off 
db2stop 
db2start
verfügbare FixPacks:
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

Lösung
Upgrade to db2_v101fp2 to avoid the signal 11.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.08.2012
22.04.2013
22.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList