SAP Knowledge Base Article - Preview

3051772 - Crash after error 208 with a stack trace signal 11 on senderror - SAP ASE

Symptom

Server crashed after error 208 followed by a stack trace with signal 11 on "senderror":

=====

Error: 208, Severity: 16, State: 1
#temptb01 not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
Current process (0x824691Y) infected with signal 11 (SIGSEGV)
Current Process is running on Engine 7
server is using elf symbols for stack decoding (125557 symbols found)
Address 0x0x000000000XXXXXXX (senderror+0xdYY), siginfo (code, address) = (YYY, 0x(nil))

...
FATAL UNHANDLED EXCEPTION: signal 0 hit while handling a previously hit signal. The server cannot continue and will shut down.
...
kepanic
kisignal
senderror
ex_printmsg
ex__doprint
exc_callprint
s_procinstall_lwp
s_renormalize
s_recompile
sequencer
execproc
s_execute
...
ueshutdown: exiting

=====


Read more...

Environment

SAP ASE 16.0 SP03 PL09

Product

SAP Adaptive Server Enterprise 16.0

Keywords

error 208 not found crash FATAL UNHANDLED EXCEPTION kepanic kisignal senderror ex_printmsg ex__doprint exc_callprint s_procinstall_lwp s_renormalize s_recompile CR 824691 CR824691 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.