Continuing from the link below which has the similar issue.
http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/3a25a069-d8fb-419b-9365-ee90a52dc617/
Exact error what I faced is below:
"Error messages:
The process could not execute 'sp_replcmds' on 'XXXServer'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Could not locate text information records for the column "XXXCol", ID 875 during command construction. (Source: MSSQLServer, Error number: 18773)
Get help: http://help/18773
The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {0004456e1:00045334:003b}.
Back up the publication database and contact Customer Support Services. (Source: MSSQLServer, Error number: 18805)
Get help: http://help/18805
The process could not execute 'sp_replcmds' on 'xxxserver'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
"
As per the link above I did not remove any subscriber but issue the following:
--Updates the record that identifies the last distributed transaction of the serverEXECsp_repldone @xactid=NULL, @xact_segno=NULL, @numtrans= 0, @time= 0, @reset= 1
-- Flushes the article cache
EXECsp_replflush
This started causing consistency issues like the below
" Command attempted:
if @@trancount > 0 rollback tran
(Transaction sequence number: 0x000444EC00003423bnn24300, Command ID: 1)
Error messages:
The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)
Get help: http://help/20598
The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)
Get help: http://help/20598
"
To resolve this I have been now identfying the articles which are causing the errors and resolving the errors.
So currently a "row was not found" error is coming and I am resolving it.
I am just wondering if there is a way that I can check the consistency for all of the articles instead of waiting for the errors one by one. Once I get this information for all tables I will fix them at once.
Secondly, I issues the repldone and flush, which I feel is a work around and not a solution.
Is there not a alternate to fix the original issue so that we may not issue the repldone which is causing subsequent issues.
Thanks.