Symptom
DSI shuts down on duplicate DDL with error messages like below:
Execution of the last DDL failed, DSI for connection 'xxx.xxx' will re-execute the transaction.
ERROR #1028 DSI EXEC(107(4) xxx.xxx) - neric/dsi/dsiqmint.c(5197)
Message from server: Message: 1913, State 1, Severity 16 -- 'There is already an index on table 'xxx' named 'xxx~P''.
THREAD FATAL ERROR #5049 DSI EXEC(107(4) xxx.xxx) - neric/dsi/dsiqmint.c(5210)
The DSI thread for database 'xxx.xxx' is being shutdown. DSI received data server error #1913 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.
...
DSI encountered error 2956 with Severity 17. It is mapped to RETRY_FOREVER. DSI will retry the transaction until the error is fixed.
ERROR #1028 DSI EXEC(107(4) xxx.xxx) - neric/dsi/dsiqmint.c(5197)
Message from server: Message: 12841, State 4, Severity 16 -- 'Partition names in each table or index must be unique. Partition name 'xxx' is specified more than once.
'.
THREAD FATAL ERROR #5049 DSI EXEC(107(4) xxx.xxx) - neric/dsi/dsiqmint.c(5210)
The DSI thread for database 'xxx.xxx' is being shutdown. DSI received data server error #12841 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.
...
Execution of the last DDL failed, DSI for connection 'xxx.xxx' will re-execute the transaction.
ERROR #1028 DSI EXEC(107(5) xxx.xxx) - neric/dsi/dsiqmint.c(5197)
Message from server: Message: 12841, State 4, Severity 16 -- 'Partition names in each table or index must be unique. Partition name 'xxx' is specified more than once.
'.
THREAD FATAL ERROR #5049 DSI EXEC(107(5) xxx.xxx) - neric/dsi/dsiqmint.c(5210)
The DSI thread for database 'xxx.xxx' is being shutdown. DSI received data server error #12841 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.
Read more...
Environment
- SAP Replication Server (SRS) 16.0
- SAP Adaptive Server Enterprise (ASE) 16.0 with Always-on Option (HADR)
- SAP Adaptive Server Enterprise (ASE) 16.0 with High Availability Disaster Recovery (HADR) for Business Suite
Product
Keywords
CR827185, CR#827185, 827185, ddl_dup_detect , 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) , 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.