Received an "Infected with Signal 11" error followed by a stack trace in the ASE errorlog:
Current process (0x0) infected with signal 11 (SIGSEGV)
Address 0x0000000100056ccc (ex_raise+0x90), siginfo (code, address) = (50, 0x7c2820404082000c)
The stack trace contains functions:
Note: The complete stack trace is available under Attachments.
- Also Error 834 reported at the same time:
Error: 834, Severity: 20, State: 3
Illegal attempt to clean buffer: BUF=0x000000031eff0890, MASS=0x000000031eff0890, Buf#=0, page=0x0000000298ded000, dbid=0, Mass vdevno=82, vpage=3682, Buf lpage=2922024, Mass stat=0x0, Buf stat=0x0, size=4096, cid=0 ('default data cache'), Pinned xdes=0x0000000000000000, spid=0.
- We could not do anything, including "shutdown".
- We had to kill the ASE process on the host
- No core dump created.
- ASE restarted without any errors and it is operational.
- SAP Adaptive Server Enterprise (ASE) 15.7
- SAP Adaptive Server Enterprise (ASE) 16.0
CR#797232, CR797232, 797232, dbreboot, shutdown_load, 3101, kill, replication, replicate, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed
About this pageThis 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.