Replication/Subscription error
in [Replication]
|
From: "Jay"<sqldba on 10 Apr 2006 11:48 I am getting following error, even though my subscriptions property is set to 336 hours & log reader agent is working fine. "The subscription has been marked inactive and must be reinitialized at the Publisher Error 21074". any help will be appreciated.
From: Hilary Cotter on 10 Apr 2006 13:18 the subscriptions are marked expired when the distribution retention is passed (14 days by default) or the history retention (48 hours by default). Change history retention to match distribution retention. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com "Jay" <sqldba(a)abc.com> wrote in message news:000c11d6231d462298008e9ba475ea33(a)ureader.com... >I am getting following error, even though my subscriptions property is set > to 336 hours & log reader agent is working fine. > "The subscription has been marked inactive and must be reinitialized at > the > Publisher Error 21074". > > any help will be appreciated.
From: "sqldba"<sqldba on 10 Apr 2006 14:19 i match the history retention to distribution retention. do i have to re-snapshot or & re-initialise. i will appreciate if you give some steps to follow to resolve this issue. I stopped Log reader & did re-snap, but still i am seeing the same error.
From: Hilary Cotter on 10 Apr 2006 15:39 Unfortunately you really reinitialize. You could do a no-sync and then run a verify, figure out which tables are out of sync, and then use a tool like Red-Gate's data compare to make sure that they are in sync. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com "sqldba" <sqldba(a)abc.com> wrote in message news:51c74805c130438a8e675af756753755(a)ureader.com... >i match the history retention to distribution retention. do i have to > re-snapshot or & re-initialise. i will appreciate if you give some steps > to > follow to resolve this issue. > > I stopped Log reader & did re-snap, but still i am seeing the same error.
From: "sqldba"<sqldba on 10 Apr 2006 16:24
Two things i did:- First> i try to reinitialize, but that didn't helped. Second> I stopped Log reader & then did re-snap, that also didn't helped. So i need help how to drop & recreate Subscription if thatis the option left for me. i will really appreciate your help to resolve this issue as i am working since morning. |