Hi All,
We have a transactional replication setup between two servers in the same network which works fine throughout the weekdays. During almost every weekend (Saturday) when the maintenance job runs, the replications starts failing with the follwoing error:
Replication-Replication Transaction-Log Reader Subsystem: agent MyServerName-MyDBName-2 scheduled for retry. The process could not execute 'sp_replcmds' on 'MyDBName'.
Or
Replication-Replication Transaction-Log Reader Subsystem: agent MyServerName-MyDBName-2 scheduled for retry. The process could not execute 'sp_repldone/sp_replcounters' on 'MyDBName'.
Or
Replication-Replication Distribution Subsystem: agent MyServerName-MyDBName-MyPublicationName-MySubscriberServerName-22 scheduled for retry. The process could not execute '{call sp_MSget_subscription_guid(22)}' on ''.
We use to get any one of the above mentioned errors almost every weekend.
Additional information:
Database Size: ~ 1 TB
Replication is done for selective tables.
Maintenance job includes the following tasks:
1) DB Integrity Check
2) Rebuild Index
3) Cleanup History
4) Maintenance Cleanup
5) Replication Reinitialization
Replication starts failing when the Rebuild Index task have started and ran for some time.
At present we are dropping the replication completely and recreating it using a new snapshot because only reinitialization does not work.
Please let me know if you need more information.
Any help will be great.
Thanks!
Indeb