Symptom
- SRS crashed with Signal 11 in the module exc_unlink_ele() called by mem_free() in the dDELSEG thread:
(14): Thread dDELSEG( ) infected with signal 11.
(14): Dumping memory trace.
(14): ***************STACK TRACE***************
(14): *****thread dDELSEG( )*******
(14): (linux_dump_all_func_stack+0x32) [0x8d6c80]
(14): (dbg_dump_stack_noarg+0x31) [0x8fc53d]
(14): (dbg_dump_stack+0x164) [0x8fd860]
(14): (exc__appDumpStack+0x105) [0x6e5dd5]
(14): (exc_terminate+0x20f) [0x6e9985]
(14): (linux_catch_signal+0x26c) [0x5476bc]
(14): /lib64/libpthread.so.0(+0x11c00) [0x7fa0849d5c00]
(14): (exc_unlink_ele+0xf0) [0x6e6018]
(14): (mem_free+0x2ca) [0x794c12]
(14): (_sqm_del_segs+0x42b) [0x4d6b53]
(14): () [0x4b1c5a]
(14): (sqm_delseg_thread_func+0x16f) [0x4b247d]
(14): (srv__start_function+0x1eb) [0xa4c56b]
(14): /lib64/libpthread.so.0(+0x96da) [0x7fa0849cd6da]
(14): /lib64/libc.so.6(clone+0x6d) [0x7fa0830bb27d]
(14): *****End of stack trace.****
(14): Internal error. Attempting to produce a core file.
- The error occurred after a chain of other issues impacting replication after the system time.
- The primary ASE and the SRS time jumped back by 1 hour (on a fly) to accommodate the daylight saving change.
- While the primary ASE was constantly dealing with resolving deadlocks and rolling back victim processes with large transactions in one of the user databases.
- SRS came up fine and had no issues after restart.
Read more...
Environment
- SAP Replication Server (SRS) 16.0 SP03 PL08
- High Availability Disaster Recovery (HADR)
Product
Keywords
CR823441, CR#823441, 823441, ulimit, unlimited , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed
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.