Symptom
- DSI thread is down
- Executing 'resume connection to <RDS.RDB>' may hit Signal 10 or Signal 11 and crash the SRS server.
- The SRS log shows the following stack traces:
- For Signal 10:
(36): /view/rs160sp03pl06_build_vu//calm/repl/svr/code/generic/dsi/hqexec.c:2959:Parallel apply failed.
(2063): Thread DSI EXEC(xxx(x) xxx.xxx) infected with signal 10.
...
(2063): Dumping memory trace.
(2063): ***************STACK TRACE***************
(2063): *****thread DSI EXEC(xxx(x) xxx.xxx)*******
(2063): pc: 0x000000000045e8a8 + 0000000000000200, exc__appDumpStack ()
(2063): pc: 0x00000000004646d8 + 000000000000048c, exc_terminate ()
(2063): pc: 0x00000000001f8c88 + 000000000000092c, sun_svr4_catch_signal ()
(2063): pc: 0x00000000003c3fa8 + 00000000000022d0, _dsi_qm_exec_cmd ()
(2063): pc: 0x000000000040d918 + 0000000000001ae8, dsie__GenerateSQL ()
(2063): pc: 0x000000000040a9e8 + 00000000000016bc, dsie__ProcessGroup ()
(2063): pc: 0x0000000000413580 + 00000000000001fc, dsie_ProcessMsgFromSched ()
(2063): pc: 0x000000000040a290 + 000000000000009c, dsie__main ()
(2063): pc: 0x0000000000408198 + 0000000000001f3c, dsie__wrap ()
(2063): pc: 0x00000000007f8c60 + 0000000000000234, srv__start_function ()
(2063): pc: 0x7e300000 + 2930f, _lwp_start ()
(2063): *****End of stack trace.****
(2063): Internal error. Attempting to produce a core file.
- For Signal 11
(1029): The first 1 transaction(s) for database 'xxx.xxx' have been logged into the exceptions log and skipped.
(49): Thread WORKER( ) infected with signal 11.
...
A parallel transaction has failed in database 'xxx.xxx'. The transaction will be executed individually.
...
(49): Dumping memory trace.
(49): ***************STACK TRACE***************
(49): *****thread WORKER( )*******
(49): pc: 0x000000000045e8a8 + 0000000000000200, exc__appDumpStack ()
(49): pc: 0x00000000004646d8 + 000000000000048c, exc_terminate ()
(49): pc: 0x00000000001f8c88 + 000000000000092c, sun_svr4_catch_signal ()
(49): pc: 0x0000000000381a90 + 0000000000001014, _dsi_exec ()
(49): pc: 0x0000000000520468 + 00000000000004b0, dsi_hq_sql_generic ()
(49): pc: 0x000000000050fa88 + 00000000000003e4, dsi_hq_continuous_repl ()
(49): pc: 0x000000000050f7b8 + 0000000000000250, dsi_hq_apply_noblk ()
(49): pc: 0x0000000000501108 + 0000000000000124, _dsi_apply_del_tbl ()
(49): pc: 0x0000000000502710 + 000000000000113c, _dsi_hq_apply_task ()
(49): pc: 0x0000000000667258 + 00000000000001d8, RSTaskExec ()
(49): pc: 0x00000000007f8c60 + 0000000000000234, srv__start_function ()
(49): pc: 0x7e300000 + 2930f, _lwp_start ()
(49): *****End of stack trace.****
(49): Internal error. Attempting to produce a core file.
Read more...
Environment
SAP Replication Server (SRS) 16.0
Product
Keywords
CR822544, CR#822544, 822544, SEGV, segmentation, storage, access, violation, fault, segfault, stacktrace, stacktrc , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , BC-SYB-REP-HET , Replication Server Heterogeneous Edition (RSHE) , BC-SYB-REP-RTL , Rep Server Real-Time Loading Edition (RTLE) , BC-SYB-REP-RSO , Rep Server Options (RSO) , BC-SYB-REP-ME , Replication Server Messaging Edition (RSME) , 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.
SAP Knowledge Base Article - Preview