Symptom
- Receiving a Signal 11 error in the thread SUB during direct load materialization.
- It is followed by a stack trace with the _sub_materialize() call:
Thread SUB(xxx) infected with signal 11.
Dumping memory trace.
***************STACK TRACE***************
*****thread SUB(xxx)*******
(linux_dump_all_func_stack+0x35) [0x8a770b]
(dbg_dump_stack_noarg+0x22) [0x8cc74c]
(dbg_dump_stack+0x10f) [0x8ccb0d]
(exc__appDumpStack+0x11b) [0x6b701b]
(exc_terminate+0x244) [0x6bab04]
(linux_catch_signal+0x248) [0x520ae8]
/lib64/libpthread.so.0(+0x11ba0) [0x7f13dce93ba0]
(_sub_materialize+0x1608) [0x502bf6]
(_sub_mat_driver+0x23b) [0x50720b]
(_sub_wrapper_main+0x7b2) [0x514b12]
(srv__start_function+0x210) [0x956e50]
/lib64/libpthread.so.0(+0x96b4) [0x7f13dce8b6b4]
/lib64/libc.so.6(clone+0x6d) [0x7f13db5852dd]
*****End of stack trace.****
Internal error. Attempting to produce a core file.
Read more...
Environment
SAP Replication Server (SRS) 16.0
Product
SAP Replication Server all versions
Keywords
CR824193, CR#824193, 824193, SEGV, segmentation, storage, access, violation, fault, segfault, stacktrace, stacktrc , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.