Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC73909 Status: Closed

DB2 ABEND WITH SIGNAL 11 DUE TO STACK CORRUPTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may abend during client termination with SIGSEV due to stack 
 
corruption. 
 
 
 
DB2DIAG messages look as follows: 
 
 
 
2010-09-01-20.13.31.626678-240 I4122045E530        LEVEL: Error 
 
PID     : 17263                TID  : 47813962492224PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
 
APPHDL  : 0-5272               APPID: XXXXX.XXXX.XXXX 
 
AUTHID  : db2inst1 
 
EDUID   : 2140                 EDUNAME: db2agent (SAMPLE) 0 
 
FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11 
 
MESSAGE : Detected client termination 
 
DATA #1 : Hexdump, 2 bytes 
 
0x00002B7C8E3F7488 : 3600 
 
6. 
 
 
 
2010-09-01-20.13.31.626804-240 I4122576E512        LEVEL: Error 
 
PID     : 17263                TID  : 47813962492224PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
 
APPHDL  : 0-5272               APPID: XXXXX.XXXX.XXXX 
 
AUTHID  : db2inst1 
 
EDUID   : 2140                 EDUNAME: db2agent (SAMPLE) 0 
 
FUNCTION: DB2 UDB, common communication, sqlcctest, probe:50 
 
MESSAGE : sqlcctest RC 
 
DATA #1 : Hexdump, 2 bytes 
 
0x00002B7C8E3F74C0 : 3600 
 
6. 
 
 
 
2010-09-01-20.13.31.626865-240 I4123089E492        LEVEL: Error 
 
PID     : 17263                TID  : 47813962492224PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
 
APPHDL  : 0-5272               APPID: XXXXX.XXXX.XXXX 
 
AUTHID  : db2inst1 
 
EDUID   : 2140                 EDUNAME: db2agent (SAMPLE) 0 
 
FUNCTION: DB2 UDB, base sys utilities, 
 
sqeAgent::AgentBreathingPoint, probe:10 
 
CALLED  : DB2 UDB, common communication, sqlcctest 
 
RETCODE : ZRC=0x00000036=54 
 
 
 
 
 
2010-09-01-20.13.32.149361-240 E4194853E1665       LEVEL: 
 
Critical 
 
PID     : 17263                TID  : 47813907966272PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
 
APPHDL  : 0-9860               APPID: XXXXX.XXXX.XXXX 
 
AUTHID  : db2inst1 
 
EDUID   : 2153                 EDUNAME: db2agent (SAMPLE) 0 
 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
 
probe:999 
 
MESSAGE : ADM14001C  An unexpected and critical error has 
 
occurred: "Trap". The 
 
          instance may have been shutdown as a result. 
 
"Automatic" FODC (First 
 
          Occurrence Data Capture) has been invoked and 
 
diagnostic information 
 
          has been recorded in directory 
 
 
 
"/home/db2inst1/sqllib/db2dump/FODC_Trap_2010-09-01-20.13.22.599 
 
157/" 
 
          . Please look in this directory for detailed evidence 
 
about what 
 
          happened and contact IBM support if necessary to 
 
diagnose the 
 
          problem. 
 
DATA #1 : Signal Number Recieved, 4 bytes 
 
11 
 
 
 
 
 
 
 
2010-09-01-20.10.16.639154-240 E3414811E517        LEVEL: Error 
 
(OS) 
 
PID     : 17263                TID  : 47815921232192PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1             NODE : 000 
 
APPHDL  : 0-9799 
 
EDUID   : 2208                 EDUNAME: db2agent () 0 
 
FUNCTION: DB2 UDB, oper system services, sqloPdbSelectSocket, 
 
probe:20 
 
MESSAGE : ZRC=0x870F0025=-2029060059=SQLO_INVH "invalid file 
 
handle" 
 
          DIA8534C An invalid file handle was encountered. 
 
CALLED  : OS, -, select                           OSERR: EBADF 
 
(9) 
 
 
 
2010-09-01-20.10.16.982814-240 I3415329E11559      LEVEL: Severe 
 
PID     : 17263                TID  : 47811676596544PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1             NODE : 000 
 
APPHDL  : 0-28624 
 
EDUID   : 1997                 EDUNAME: db2agent () 0 
 
FUNCTION: DB2 UDB, base sys utilities, sqlePeekRequest, probe:10 
 
MESSAGE : Possible stack corruption detected! 
 
DATA #1 : Hexdump, 2200 bytes 
 
 
 
 
 
PROCESS STACK may look similar to this: 
 
 
 
 
 
        ossDumpStackTraceEx 
 
1        OSSTrapFile::dumpEx 
 
2        OSSTrapFile::dump 
 
3        sqlo_trce 
 
4        sqloEDUCodeTrapHandler 
 
5        __invoke_dynamic_linker 
 
6        sqlcctest 
 
7        sqeAgent::AgentBreathingPoint 
 
8        sqldFetchDirect 
 
9        sqldDataFetch 
 
10       sqli_proc_leaf
Problem Summary:
DB2 ABEND WITH SIGNAL 11 DUE TO STACK CORRUPTION
Local Fix:
To possibly avoid the issue, make sure that number of open 
files(nofiles, ulimit -n) ulimit is not set greater than 64K. 
 
1. To get the value for nofiles set: 
 
ulimit -n 
 
2. If it is greater than 64K, please set it to 64K: 
 
ulimit -n 65536
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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

Solution
Fixed in DB2 V9.7 FP4 
 
To possibly avoid the issue, make sure that number of open 
 
files(nofiles, ulimit -n) ulimit is not set greater than 64K. 
 
1. To get the value for nofiles set: 
 
ulimit -n 
 
2. If it is greater than 64K, please set it to 64K: 
 
ulimit -n 65536
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.01.2011
29.04.2011
29.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.