- DSI connection went down due to exception. An example is the target ASE reports error 1105.
- After resolved the target ASE issue, resume DSI conenction crashed the replication server with infected with 11.
- The following messages can be seen in the replication server errorlog
ERROR #1028 DSI EXEC(282(1) TargetASE.targetdb) - neric/dsi/dsiqmint.c(4871)
Message from server: Message: 1105, State 4, Severity 17 -- 'Can't allocate space for object 'syslogs' in database 'Targetdb' because 'logsegment' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE t.
THREAD FATAL ERROR #5049 DSI EXEC(282(1) TargetASE.Targetdb) - neric/dsi/dsiqmint.c(4884)
The DSI thread for database 'TargetASE.Targetdb' is being shutdown. DSI received data server error #1105 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #0 mapped from input command #0 of the failed transaction.
The DSI thread for database 'TargetASE.Targetdb' is shutdown.
The DSI thread for database 'TargetASE.Targetdb' is started.
(2533): Thread DSI EXEC(282(1) TargetASE.Targetdb) infected with signal 11.
(2533): Dumping memory trace.
(2533): ***************STACK TRACE***************
(2533): *****thread DSI EXEC(282(1) TargetASE.Targetdb)*******
(2533): pc: 0x0000000000861bbc + 00000000000000e3, dbg_dump_stack ()
(2533): *****End of stack trace.****
(2533): Internal error. Attempting to produce a core file
SAP Replication Server 15.7.1
SAP Replication Server 15.7
KBA , BC-SYB-REP , Sybase Replication Server (standalone) , 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.