Error Number 18764
Contents |
failed to construct a replicated command from log sequence number (LSN)” ★★★★★★★★★★★★★★★ sequelguyDecember 30, 20087 source mssql_repl error number mssql_repl22037 0 0 0
Could Not Locate Text Information Records For The Column During Command Construction
Recently we encountered a case where in the Log Reader Agent fails to run and the following source: mssql_repl, error number: mssql_repl20011 error is reported in the Replication MonitorError messages:The process could not execute ‘sp_replcmds' on ‘TXDAL01410'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)Get help: http://help/MSSQL_REPL20011Execution of filter stored procedure 2048634987 failed. the process could not execute sp_replcmds on See the SQL Server errorlog for more information. (Source: MSSQLServer, Error number: 18764)Get help: http://help/18764The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {0001d651:00002a49:0006}. Back up the publication database and contact Customer Support Services. (Source: MSSQLServer, Error number: 18805)Get help: http://help/18805The process could not execute ‘sp_replcmds' on ‘TXDAL01410'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)Get help: http://help/MSSQL_REPL22037 CAUSE=====The above Error indicates the Log Reader Agent is stuck at LSN {0001d651:00002a49:0006} and is not able to read and create a command for this LSN.As the Log Reader Agent is stuck at the LSN, it is not moving ahead and since we can have only 1 Log Reader Agent in Transactional Replication which is used for all the publications. All the publications is showing error in the replication monitor and is not moving ahead.We checked the transaction at the LSN {0001d651:00002a49:0006}. From the above Error we see “Execution of filter stored procedure 2048634987 failed”We checked the Filter Stored Procedure ID from sysarticles and found that it was the filter stored procedure for table dbo.bookingSelect * from sysarticles where filter=2048634987However the entry of the filter stored procedure was missing in the sysobjects tables which indicate that the filter stored procedure was deleted due to some reason. To confirm this we used the following queryselect * from (select art.name as article_n
with From PublisherReplication MonitorReplication - publisher to Distribution History, we have the below error :The process could not execute 'sp_replcmds' on '. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)Get help: http://help/MSSQL_REPL20011Execution of filter stored procedure 1820181880 failed. See the SQL Server errorlog for more information. (Source: MSSQLServer, Error number: 18764)Get help: http://help/18764The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {00026ef8:00039201:0004}. Back up the publication database and contact Customer Support Services. (Source: MSSQLServer, Error number: 18805)Get help: http://help/18805The process could not execute 'sp_replcmds' on ''. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)Get help: http://help/MSSQL_REPL22037 Publisher SQL Server - Error Log https://blogs.msdn.microsoft.com/sqlserverfaq/2008/12/30/log-reader-agent-fails-with-the-error-the-log-reader-agent-failed-to-construct-a-replicated-command-from-log-sequence-number-lsn/ No error From Publisher, publisher databaserun the below query. That might some error in replication filtering.Select * from sysarticles where filter=1014603790 From SQLServer-> Replication->Local Publication->ReplicationName-> right click -> Properties-> Filter RowsCheck the condition as well Posted by soonyu at 11:54 AM No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) You might also like: Follow by Email Blog Archive ► 2016 (5) http://soonyu-sql.blogspot.com/2014/08/replication-spreplcmds-execution-of.html ► July (1) ► May (2) ► April (1) ► January (1) ► 2015 (3) ► August (2) ► January (1) ▼ 2014 (8) ► December (1) ► November (1) ► September (1) ▼ August (3) Replication - sp_replcmds; Execution of filter sto... MSSQL disaster recovery Index best practice resource ► April (1) ► February (1) ► 2013 (19) ► August (7) ► July (1) ► May (3) ► April (3) ► March (1) ► January (4) ► 2012 (8) ► December (1) ► September (2) ► August (2) ► February (1) ► January (2) ► 2011 (10) ► November (1) ► October (2) ► June (2) ► March (2) ► January (3) ► 2010 (23) ► December (8) ► November (2) ► October (2) ► July (1) ► May (3) ► March (2) ► February (2) ► January (3) ► 2009 (12) ► December (1) ► November (2) ► October (7) ► September (1) ► March (1) ► 2008 (9) ► November (5) ► October (1) ► August (1) ► April (1) ► January (1) ► 2007 (1) ► August (1) ► 2006 (6) ► November (1) ► September (2) ► July (2) ► June (1) Links SQL JOB S
Oracle 10g Oracle 11g MySQL MongoDB Vertica DB MS Access Netapp Linux Powershell Windows Replication - Execution of filter stored procedure 678449641failed. November https://dbamohsin.wordpress.com/2009/11/ 26, 2009 Leave a comment ERROR: Error messages:The process could not execute ‘sp_replcmds' on ‘TCY-SQL01\SQLDEV'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)Get help: http://help/MSSQL_REPL20011Execution of filter stored procedure 678449641 failed. See the http://dbaspot.com/ms-sqlserver/235905-mssqlserver-18805-failed-construct-replicated-command-log-sequence-number.html SQL Server errorlog for more information. (Source: MSSQLServer, Error number: 18764)Get help: http://help/18764The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {000ff0ac:00000520:003e}. Back up error number the publication database and contact Customer Support Services. (Source: MSSQLServer, Error number: 18805)Get help: http://help/18805The process could not execute ‘sp_replcmds' on ‘TCY-SQL01\SQLDEV'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)Get help: http://help/MSSQL_REPL22037 CAUSE The above Error indicates the Log Reader Agent is stuck at LSN {0001d651:00002a49:0006} and is not able to read and create a command for this LSN.As the Log Reader Agent error number 18764 is stuck at the LSN, it is not moving ahead and since we can have only 1 Log Reader Agent in Transactional Replication which is used for all the publications. All the publications is showing error in the replication monitor and is not moving ahead. We checked the transaction at the LSN {0001d651:00002a49:0006}. From the above Error we see “Execution of filter stored procedure 2048634987 failed” We checked the Filter Stored Procedure ID from sysarticles and found that it was the filter stored procedure for table dbo.booking Select * from sysarticles where filter=2048634987However the entry of the filter stored procedure was missing in the sysobjects tables which indicate that the filter stored procedure was deleted due to some reason. To confirm this we used the following query select * from (select art.name as article_name, art.pubid as publication_id, art.artid as article_id, art.filter as filter_proc_id, isnull(obj.name,‘## MISSING!! ##') as filter_proc_namefrom sysarticles art left outer join sys.objects obj on art.filter = obj.object_idwhere art.filter > 0)as results -- and obj.name is null (use when only the mismatched articles where required).where filter_proc_name=‘## MISSI