home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT06801 Status: Closed

CRASH IN SQLEX_FIND_GROUP WHEN CUMULATIVE LENGTH OF GROUP NAMES RETURNED
FOR AN USER ID IS GREATER THEN 64K

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
There is a potential for a crash in  sqlex_find_group when 
cumulative length of group names  returned for an user id is 
greater then 64K. 
 
Stack similar to: 
DB2 build information: DB2 v9.7.0.6 special_30249 SQL09076 
timestamp: 2015-01-23-10.14.28.601216 
instance name: db2inst1.000 
EDU name     : db2agent (SAMPLE) 0 
EDU ID       : 232 
Signal #11 
uname: S:Linux R:2.6.18-308.13.1.el5 V:#1 SMP Thu Jul 26 
05:45:09 EDT 2012 M:x86_64 N:hz867c1n7 
process id: 25547 
thread id : 46979170167104 (0x2ABA30BFE940) 
</Header> 
<SignalDetails> 
<Siginfo_t length="128"> 
Signal #11 (SIGSEGV): si_addr is 0x0000000000000000, si_code is 
0x00000080 (SI_KERNEL:Send by kernel.) 
</SignalDetails> 
<ResourceLimits> 
Data seg top [sbrk(0)] = 0x0000000002704000 
Cur cpu time limit (seconds)  = 0xFFFFFFFF 
Cur file limit (bytes)  = 0xFFFFFFFF 
Cur data size (bytes)  = 0xFFFFFFFF 
Cur stack size (bytes) = 0x00A00000 
Cur core size (bytes)  = 0x3D090000 
Cur nofiles (descriptors)  = 0x0000FFFE 
Cur memory size (bytes)  = 0xFFFFFFFF 
</ResourceLimits> 
<Registers> 
   rax 0x0000000000000000  rbx 0x6f743c3e656d6974 
   rcx 0x0000000000006f63  rdx 0x0000000000000024 
 
rbp 0x6d6d6f635f6c6174  rsp 0x00002aba30bf23f8 
   rsi 0x00002aba30bf2344  rdi 0x00002aba30bf22c0 
rflags 0x0000000000010202  rip 0x00002aaaabff567f 
   r8  0x0000000000000002  r9  0x0000000000000002 
   r10 0x00002aaab3b90406  r11 0x000000000041830a 
   r12 0x3e656d69745f7469  r13 0x6c61746f742f3c30 
   r14 0x0000000000000000  r15 0x5f74696d6d6f635f 
</Registers> 
<POFDisassembly> 
 _Z16sqlex_find_groupPc14sqlo_mem_descr + 0x0203 
(/var/ibmdb2/db2inst1/sq 
llib/lib64/libdb2e.so.1) 
 
        0x00002AAAABFF567F : C3BD06000020EBE7 
</POFDisassembly> 
<StackTrace> 
 
 
Diag log  entry 
 
 
2015-01-23-10.14.29.098656-300 I953892E519         LEVEL: Severe 
PID     : 25547                TID  : 46979170167104PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-42121              APPID: 
10.184.115.248.36738.1501231514 
AUTHID  : ETLMIGP 
EDUID   : 232                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:180 
MESSAGE : Stack analysis failed due to incomplete  'StackTrace' 
section in trap 
          file. 
 
2015-01-23-10.14.29.099039-300 I954412E527         LEVEL: Severe 
PID     : 25547                TID  : 46979170167104PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-42121              APPID: 
10.184.115.248.36738.1501231514 
AUTHID  : ETLMIGP 
EDUID   : 232                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:190 
MESSAGE : Stack analysis failed, which implies stack corruption 
or failed to do 
          'stack walk'. 
 
 
====================================
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 Fix Pack 7                           * 
****************************************************************
Local Fix:
Reduce the number of groups for the user id
Solution
First fixed in Version 10.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.01.2015
02.02.2016
02.02.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList