| Groups | Blog | Home |
sql server replication : Subscriptions being marked inactive
Hi everyone,
We have transactional replication between a data entry and reporting servers. Now, in addition, we added another subscriber which is a test server. This new subscriber has a strange problem that stopping and starting a distribution agent can cause a subscription to be marked inactive, or sometimes it will mark subscriptions inactive for no apparent reason whatsoever. This is a part of a typical error message: The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated Subscriptions never expire is set on all publications. Thanks,
Set the history retention period to the same time period as your retention
period. Examine msrepl_errors and the distribution agent history to find out what is causing this agent to fail, and to expire. -- 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 [quoted text, click to view] "Mor DeRor" <Mor DeRor@discussions.microsoft.com> wrote in message news:8DF65739-8E92-4E58-9D5B-1BCF602E8E6A@microsoft.com... > Hi everyone, > > We have transactional replication between a data entry and reporting > servers. Now, in addition, we added another subscriber which is a test > server. This new subscriber has a strange problem that stopping and > starting > a distribution agent can cause a subscription to be marked inactive, or > sometimes it will mark subscriptions inactive for no apparent reason > whatsoever. > > This is a part of a typical error message: > The subscription(s) have been marked inactive and must be reinitialized. > NoSync subscriptions will need to be dropped and recreated > > Subscriptions never expire is set on all publications. > > Thanks, > > Mor
Thanks, Hilary,
But these settings that you are talking about are publication specific. The problem, howver is subcsriber specific. I think this way because there are two subscriptions to the same publication, and only one of them is giving errors. Here is an example: "Replication-Replication Distribution Subsystem: agent <DISTRIBUTION AGENT JOB NAME> failed. The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated." MSREPL_ERROR for the time of error shows error text NULL and command_id -1 [quoted text, click to view] "Hilary Cotter" wrote:
> Set the history retention period to the same time period as your retention > period. Examine msrepl_errors and the distribution agent history to find out > what is causing this agent to fail, and to expire. > > -- > 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 > > > > "Mor DeRor" <Mor DeRor@discussions.microsoft.com> wrote in message > news:8DF65739-8E92-4E58-9D5B-1BCF602E8E6A@microsoft.com... > > Hi everyone, > > > > We have transactional replication between a data entry and reporting > > servers. Now, in addition, we added another subscriber which is a test > > server. This new subscriber has a strange problem that stopping and > > starting > > a distribution agent can cause a subscription to be marked inactive, or > > sometimes it will mark subscriptions inactive for no apparent reason > > whatsoever. > > > > This is a part of a typical error message: > > The subscription(s) have been marked inactive and must be reinitialized. > > NoSync subscriptions will need to be dropped and recreated > > > > Subscriptions never expire is set on all publications. > > > > Thanks, > > > > Mor > >
Expiration is the lesser of the retention setting, transaction retention
setting, and history retention setting. So with a large retention you must set the transaction and history retention to the same amount otherwise it will expire. -- 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 [quoted text, click to view] "Mor DeRor" <MorDeRor@discussions.microsoft.com> wrote in message news:3FDE0025-3DD4-498F-91C3-DF5EC9B98918@microsoft.com... > Thanks, Hilary, > > But these settings that you are talking about are publication specific. > The > problem, howver is subcsriber specific. I think this way because there are > two subscriptions to the same publication, and only one of them is giving > errors. > Here is an example: > "Replication-Replication Distribution Subsystem: agent <DISTRIBUTION AGENT > JOB NAME> failed. The subscription(s) have been marked inactive and must > be > reinitialized. NoSync subscriptions will need to be dropped and > recreated." > > MSREPL_ERROR for the time of error shows error text NULL and command_id -1 > > "Hilary Cotter" wrote: > >> Set the history retention period to the same time period as your >> retention >> period. Examine msrepl_errors and the distribution agent history to find >> out >> what is causing this agent to fail, and to expire. >> >> -- >> 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 >> >> >> >> "Mor DeRor" <Mor DeRor@discussions.microsoft.com> wrote in message >> news:8DF65739-8E92-4E58-9D5B-1BCF602E8E6A@microsoft.com... >> > Hi everyone, >> > >> > We have transactional replication between a data entry and reporting >> > servers. Now, in addition, we added another subscriber which is a test >> > server. This new subscriber has a strange problem that stopping and >> > starting >> > a distribution agent can cause a subscription to be marked inactive, or >> > sometimes it will mark subscriptions inactive for no apparent reason >> > whatsoever. >> > >> > This is a part of a typical error message: >> > The subscription(s) have been marked inactive and must be >> > reinitialized. >> > NoSync subscriptions will need to be dropped and recreated >> > >> > Subscriptions never expire is set on all publications. >> > >> > Thanks, >> > >> > Mor >> >> >>
Are you talking about the "transaction retention" and "history retention"
settings that are available on the distributor? I really need to find something subscriber specific, otherwise it does not make sense that two subscriber that use the same publisher, and same distributor should have different behaviour. [quoted text, click to view] "Hilary Cotter" wrote:
> Expiration is the lesser of the retention setting, transaction retention > setting, and history retention setting. So with a large retention you must > set the transaction and history retention to the same amount otherwise it > will expire. > > -- > 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 > > > > "Mor DeRor" <MorDeRor@discussions.microsoft.com> wrote in message > news:3FDE0025-3DD4-498F-91C3-DF5EC9B98918@microsoft.com... > > Thanks, Hilary, > > > > But these settings that you are talking about are publication specific. > > The > > problem, howver is subcsriber specific. I think this way because there are > > two subscriptions to the same publication, and only one of them is giving > > errors. > > Here is an example: > > "Replication-Replication Distribution Subsystem: agent <DISTRIBUTION AGENT > > JOB NAME> failed. The subscription(s) have been marked inactive and must > > be > > reinitialized. NoSync subscriptions will need to be dropped and > > recreated." > > > > MSREPL_ERROR for the time of error shows error text NULL and command_id -1 > > > > "Hilary Cotter" wrote: > > > >> Set the history retention period to the same time period as your > >> retention > >> period. Examine msrepl_errors and the distribution agent history to find > >> out > >> what is causing this agent to fail, and to expire. > >> > >> -- > >> 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 > >> > >> > >> > >> "Mor DeRor" <Mor DeRor@discussions.microsoft.com> wrote in message > >> news:8DF65739-8E92-4E58-9D5B-1BCF602E8E6A@microsoft.com... > >> > Hi everyone, > >> > > >> > We have transactional replication between a data entry and reporting > >> > servers. Now, in addition, we added another subscriber which is a test > >> > server. This new subscriber has a strange problem that stopping and > >> > starting > >> > a distribution agent can cause a subscription to be marked inactive, or > >> > sometimes it will mark subscriptions inactive for no apparent reason > >> > whatsoever. > >> > > >> > This is a part of a typical error message: > >> > The subscription(s) have been marked inactive and must be > >> > reinitialized. > >> > NoSync subscriptions will need to be dropped and recreated > >> > > >> > Subscriptions never expire is set on all publications. > >> > > >> > Thanks, > >> > > >> > Mor > >> > >> > >> > >
Yes, that is what I imagine is the problem. But I don't know of any setting
that controls subscriber specific timeouts. [quoted text, click to view] "Paul Ibison" wrote:
> It still could be 'subscriber-specific', if one subscriber hasn't > synchronized for a while whereas the other synchronises more frequently - > perhaps this is the case? > Paul Ibison > >
It still could be 'subscriber-specific', if one subscriber hasn't
synchronized for a while whereas the other synchronises more frequently - perhaps this is the case? Paul Ibison
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
October 2008
| home · blog · groups | Questions? Comments? Contact the dn |