cancel
Showing results for 
Search instead for 
Did you mean: 

server crash DBSTATE Caught signal 11(SIGSEGV) any idea to check why?

Former Member
0 Kudos

Hi,

today a server crash with DBSTATE Caught signal 11(SIGSEGV), any idea how to check why?

in this knldia20100712.txt have the full knldiag the error is at line 10975 on 2010-07-12 16:43:57.

i just restarted the system and all comes back again, but there is a way to check, predict or avoid this to occurs again?

best regards

Clóvis

Accepted Solutions (1)

Accepted Solutions (1)

lbreddemann
Active Contributor
0 Kudos

HI Clovis,

looks like this : http://maxdb.sap.com/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1138883

If this would be mine DB, I'd install the current available patch, run the parameter checker (and correct the settings) and see if the issue reoccurs (shouldn't).

regards,

Lars

Former Member
0 Kudos

Hi Lars,

if i understand you mean that in some internal user function, one of these errors:

-4005: Unknown column name

-8006: Data types must be compatible

occurred, causing the system crash, right?

what i dont understand is what you mean with "and correct the settings", you see any wrong settings in my knldiag, that can cause this problem?

regards

Clóvis

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

The kernel crashes here:

2010-07-12 16:43:57     0 ERR 11599 BTRACE      3: 0x0000000000efba48 en81_CrashSignalHandler +0x00e8
2010-07-12 16:43:57     0 ERR 11599 BTRACE          /pex/opt/sdb/7603/pgm/kernel
2010-07-12 16:43:57     0 ERR 11599 BTRACE         Frameinfo [0x0]
2010-07-12 16:43:57     0 ERR 11599 BTRACE      4: 0x0000003757f0c430 __sched_getscheduler@@GLIBC_2.2.5 +0xc430
2010-07-12 16:43:57     0 ERR 11599 BTRACE          /lib64/tls/libpthread-2.3.4.so
2010-07-12 16:43:57     0 ERR 11599 BTRACE         Frameinfo [0x0]
2010-07-12 16:43:57     0 ERR 11599 BTRACE      5: 0x000000000065f50e a10refresh_cache +0x008e
2010-07-12 16:43:57     0 ERR 11599 BTRACE          /pex/opt/sdb/7603/pgm/kernel

This seems to be an issue with the thread library.

You're using a pretty old version:

VERSION 'Kernel 7.6.03 Build 007-123-157-515'

I'd update to the latest build (7.6.6.x) available.

What exact operating system and patch level is that system?

markus

Former Member
0 Kudos

Hi, Markus

the operating system is a RHEL 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux

thanks for your reply

Clóvis