Skip to Content
0
Former Member
Jun 24, 2010 at 09:11 AM

MaxDB Database error signal 11 code 2 (ILL_ILLOPN:illegal operand)

88 Views

Dear all,

this morning we ran into a database error with our maxdb which caused it to crash. After a manual restart it seems to run fine again. It is the first crash since we started the database about 2 years ago. The applications (perl) connecting against the database have not changed during the last days, so we have no idea what the possible error could be. The MaxDB is running on Solaris 10 Any help is appreciated.

Sebastian

Below is the relevant part from the MaxDB error log

47: 2010-06-24 09:34:06 0 ERR 11330 COREHAND ABORTING due to signal 11

<snip>

185: 2010-06-24 09:34:06 0 ERR 11330 COREHAND dump of siginfo content:

186: 2010-06-24 09:34:06 0 ERR 11330 COREHAND signal 11 (SIGSEGV)

187: 2010-06-24 09:34:06 0 ERR 11330 COREHAND code 2 (ILL_ILLOPN:illegal operand)

188: 2010-06-24 09:34:06 0 ERR 11330 COREHAND errno 0

189: 2010-06-24 09:34:06 0 ERR 11330 COREHAND value(int) 0

190: 2010-06-24 09:34:06 0 ERR 11330 COREHAND value(ptr) @0

191: 2010-06-24 09:34:06 0 ERR 11330 COREHAND pid 17712073

192: 2010-06-24 09:34:06 0 ERR 11330 COREHAND addr @10E43C9

193: 2010-06-24 09:34:06 0 ERR 11599 BTRACE analysing LVCMem_Allocator_001

194: 2010-06-24 09:34:06 0 ERR 11599 BTRACE

195: 2010-06-24 09:34:06 0 ERR 11599 BTRACE no problems detected in LVCMem_Allocator_001

196: 2010-06-24 09:34:09 0 ERR 12006 DBCRASH Kernel exited without core and exit status 0x2f00

197: 2010-06-24 09:34:09 0 ERR 12008 DBCRASH Kernel exited due to reentered signal handler

198: 2010-06-24 09:34:12 ___ Stopping GMT 2010-06-24 07:34:12 7.6.05 Build 009-123-191-997

Edited by: Sebastian2 on Jun 24, 2010 11:12 AM