Fatal Error 5049 Dsi
block. Replication Server error message block: H. 2006/06/15 20:52:28. THREAD FATAL ERROR #5049 DSI EXEC(104(3) WESTERNDS.westDB) - dsiqmint.c(3252) The DSI thread for database ‘WESTERNDS.westDB' is being shutdown. DSI received data server error #102 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #1 mapped from input command #2 of the failed transaction. I. 2006/06/15 20:52:28. The DSI thread for database ‘WESTERNDS.westDB' is shutdown. Analysis of the Replication Server Error Message Error Message Text Explanation H. 2006/06/15 20:52:28. THREAD FATAL ERROR #5049 DSI EXEC(104(3) WESTERNDS.westDB) - dsiqmint.c(3252) This is the first error. The H identifies the error as a thread termination error. This message shows that the Data Server Interface (DSI) thread terminated. The error message includes the dataserver.database name where the error occurred, the internal Replication Server module (dsiqmint.c), and the line of code (3252) where the error occurred. The DSI received data server error # 102 which is mapped to STOP_REPLICATION. See the logged data server errors for more information. This Adaptive Server error message identifies the cause of the problem. Find a description for Adaptive Server error 102 by: Finding the error in the Adaptive Server error log (the error would occur at approximately the same time as it occurred in the Replication Server error log), Performing a select * from sysmessages where error = 102 in the master database, or Looking up the number in the Adaptive Server Enterprise Troubleshooting and Error Messages Guide. The Adaptive Server Enterprise Troubleshooting and Error Messages Guide describes error 102 as invalid syntax near %s for a Transact-SQL™ statement. It also provides suggestions about what might be causing this err
out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 14 of 14 Thread: Replication problem Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 04-19-04,05:10 #1 Wilson77 View Profile View Forum Posts Registered User Join Date Apr 2004 Posts 79 Unanswered: Replication problem Hi I am facing following error message as I am unable to start DSI thread for my user database. http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc35920.1560/doc/html/san1279229916401.html I am using warm standby replication method and version used is Replication version is Replication Server/12.5/EBF 10505/PC Intel/Windows NT 4.0/1/OPT/Tue Jul 16 19:36:13 PDT 2002 I. 2004/04/19 10:34:45. A parallel transaction has failed in database 'MySrv.DB'. The transaction will be executed individually. I. 2004/04/19 10:34:45. Message from server: Message: 11065, State 1, Severity 10 -- ''SET IDENTITY_INSERT' is ON for table 'dbo.user_table'. '. H. 2004/04/19 10:34:45. THREAD FATAL ERROR #5049 DSI EXEC(124(2) MySrv.DB) - dsiqmint.c(2975) The http://www.dbforums.com/showthread.php?994495-Replication-problem DSI thread for database 'MySrv.DB' is being shutdown. DSI received data server error #11065 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #1 mapped from input command #3 of the failed transaction. Can a replication guru help me in solving this issue. Thanks .. Wilson Reply With Quote 04-19-04,08:14 #2 fadace View Profile View Forum Posts Visit Homepage Registered User Join Date Nov 2002 Location Switzerland Posts 524 Be sure that 1) all logins existing on the Primary server are existing in the standby side, using the same suid: each DDL cmmand is executed using the calling user, and not the maintenance user. 2) the maintenance user is aliased as DBO Reply With Quote 04-19-04,11:13 #3 Wilson77 View Profile View Forum Posts Registered User Join Date Apr 2004 Posts 79 Replicatiopn problem Thanks for your response. But can you please explain a bit more in details about the calling user. What do u mean by calling user..?? Best Rgds Wilson Reply With Quote 04-20-04,08:52 #4 fadace View Profile View Forum Posts Visit Homepage Registered User Join Date Nov 2002 Location Switzerland Posts 524 On warm Standby environment: 1) each insert/update/delete (DML command) is replicated to the Standby database and executed by the maintenance user 1) each DDL command is
SAP Replication Server (SRS) DSI thread with an error: ERROR #1028 DSI EXEC(109(1) OnASE160.RDB) - neric/dsi/dsiqmint.c(4781)Message from server: Message: 17260, State 1, Severity 16 -- 'Can't run sp_rename from within fatal error a transaction.'.THREAD FATAL ERROR #5049 DSI EXEC(109(1) OnASE160.RDB) - neric/dsi/dsiqmint.c(4794)The DSI thread for database 'OnASE160.RDB' is being shutdown. DSI received data server error #17260 which is mapped to STOP_REPLICATION. See logged data server errors fatal error 5049 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 'OnASE160.RDB' is shutdown Read more... Product SAP Replication Server all versions Keywords repserver , KBA , BC-SYB-REP , Sybase Replication Server (standalone) About this page This 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. Terms of use | Copyright | Trademark | Legal Disclosure | Privacy