DB2 - Problem description
Problem IC94760 | Status: Closed |
XQUERY MAY GET SQL1224N AND SIGSEGV | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
A complicated XQUERY statement may receive SQL1224N error and generate a sigsegv trap file. Here is an example trap file, it shows xml4c function name and its file name libDB2xml4c.so. ... <DB2TrapFile version="1.0"> <Trap> <Header> DB2 build information: DB2 v9.7.0.4 s110330 SQL09074 timestamp: 2013-07-31-03.00.43.896944 instance name: hidehy.000 EDU name : db2agent (TEST) EDU ID : 37 Signal #11 uname: S:Linux R:2.6.16.60-0.85.1-smp V:#1 SMP Thu Mar 17 process id: 14822 thread id : 46912933718336 (0x2AAAC4BFE940) </Header> <SignalDetails> <Siginfo_t length="128"> 0B000000 00000000 02000000 00000000 A80F81C4 AA2A0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 </Siginfo_t> Signal #11 (SIGSEGV): si_addr is 0x00002AAAC4810FA8, si_code is 0x00000002 (SEGV_ACCERR:Invalid permissions for mapped object.) </SignalDetails> <ResourceLimits> Data seg top [sbrk(0)] = 0x00000000006A0000 Cur cpu time limit (seconds) = 0xFFFFFFFF Cur file limit (bytes) = 0xFFFFFFFF Cur data size (bytes) = 0xFFFFFFFF Cur stack size (bytes) = 0x00800000 Cur core size (bytes) = 0xFFFFFFFF Cur nofiles (descriptors) = 0x0000FFFE Cur memory size (bytes) = 0xFFFFFFFF </ResourceLimits> <Registers> rax 0x00002aaab1cb56c0 rbx 0x0000000000005332 rcx 0x00002aaac4811060 rdx 0x00002aaaca41eb68 rbp 0x0000000000000000 rsp 0x00002aaac4810fb0 rsi 0x00002aaac4bf7630 rdi 0x00002aaaca45df08 rflags 0x0000000000010293 rip 0x00002aaab1843872 r8 0x0000000000000001 r9 0x0000000000000000 r10 0x0000000000000001 r11 0x0000000000000000 r12 0x00002aaaca45df08 r13 0x00002aaac4bf7630 r14 0x00002aaaca41eb68 r15 0x0000000000000001 </Registers> <POFDisassembly> _ZN9xml4c_5_717RegularExpression5matchEPNS0_7ContextEPKNS_2OpEis + 0x053c (/home/hotellnx97/hidehy/sqllib/lib64/libDB2xml4c.so.57) 0x00002AAAB1843872 : E89977F3FF0FB6C0 </POFDisassembly> <StackTrace> -----FUNC-ADDR---- ------FUNCTION + OFFSET------ 0x00002AAAB03C4E2F ossDumpStackTraceEx + 0x01ef (/home/hotellnx97/hidehy/sqllib/lib64/libdb2osse.so.1) 0x00002AAAB03BFBEE _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00cc (/home/hotellnx97/hidehy/sqllib/lib64/libdb2osse.so.1) 0x00002AAAAD4CACAB sqlo_trce + 0x03fb (/home/hotellnx97/hidehy/sqllib/lib64/libdb2e.so.1) 0x00002AAAAD510392 sqloEDUCodeTrapHandler + 0x0266 (/home/hotellnx97/hidehy/sqllib/lib64/libdb2e.so.1) 0x00002AAAAABD4D60 address: 0x00002AAAAABD4D60 ; dladdress: 0x00002AAAAABC7000 ; offset in lib: 0x000000000000DD60 ; (/lib64/libpthread.so.0) 0x00002AAAB1843872 _ZN9xml4c_5_717RegularExpression5matchEPNS0_7ContextEPKNS_2OpEis + 0x053c (/home/hotellnx97/hidehy/sqllib/lib64/libDB2xml4c.so.57) 0x00002AAAB18437CC _ZN9xml4c_5_717RegularExpression5matchEPNS0_7ContextEPKNS_2OpEis + 0x0496 (/home/hotellnx97/hidehy/sqllib/lib64/libDB2xml4c.so.57) ... The problem exists on V9.5, V9.7, V9.8 and V10.1. But V10.5 does not have this problem. Users may work around this problem by upgrading to V10.5. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 10.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 FixPack 4. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.08.2013 03.06.2014 03.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |