dbTalk Databases Forums  

Subscription marked inactive in SQL 2008

microsoft.public.sqlserver.replication microsoft.public.sqlserver.replication


Discuss Subscription marked inactive in SQL 2008 in the microsoft.public.sqlserver.replication forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
OceanDeep via SQLMonster.com
 
Posts: n/a

Default Subscription marked inactive in SQL 2008 - 08-12-2010 , 04:07 PM






We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber. The publisher and distributor are on the same server.

Out of nowhere, I received the following message.

The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.

The subscription setting in the publisher is 'never expire'. The retention
settings in the distributor are as follows:

Transaction retention: At least 0 hours and but not more than 72 hours.
History retention: store replication performance History at least 48 hours.

Since we upgrade to SQL 2005 and SQL 2008, I haven't encountered this error
for over 2 years as the default is set to 'never expire' I think. So what
happened to my subscription? why all of a sudden, this error comes up. What
is the solution for it?


Any help on this is very much appreciated.

od

--
Message posted via http://www.sqlmonster.com

Reply With Quote
  #2  
Old   
Ben Thul
 
Posts: n/a

Default Re: Subscription marked inactive in SQL 2008 - 08-12-2010 , 10:31 PM






How do you monitor your replication? Do you know that your subscriber
wasn't more that 72 hours behind the publisher? If it got outside of
that threshold, that would make the subscription expire, regardless of
settings. Other than that, I can't think of another reason why that
would happen.
--
Ben
On Aug 12, 4:07*pm, "OceanDeep via SQLMonster.com" <u46587@uwe> wrote:
Quote:
We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber. *The publisher and distributor are on the same server.

Out of nowhere, I received the following message.

The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.

The subscription setting in the publisher is 'never expire'. * The retention
settings in the distributor are as follows:

Transaction retention: At least 0 hours and but not more than 72 hours.
History retention: *store replication performance History at least 48 hours.

Since we upgrade to SQL 2005 and SQL 2008, I haven't encountered this error
for over 2 years as the default is set to 'never expire' I think. *So what
happened to my subscription? *why all of a sudden, this error comes up.*What
is the solution for it?

Any help on this is very much appreciated.

od

--
Message posted viahttp://www.sqlmonster.com

Reply With Quote
  #3  
Old   
Nick Fairway
 
Posts: n/a

Default Re: Subscription marked inactive in SQL 2008 - 03-25-2011 , 07:37 AM



We are having a similar issue on SQL2005. Two of 8 subscriptions have this error. These subscriptions have been working for months and then suddenly 2 will not work. Even tried dropping all subscriptions and adding them in again - the same 2 always error out immediately before we even initialise with "The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated."

Did anyone find the solution?

Quote:
On Thursday, August 12, 2010 9:07 PM OceanDeep via SQLMonster.com wrote:

We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber. The publisher and distributor are on the same server.

Out of nowhere, I received the following message.

The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.

The subscription setting in the publisher is 'never expire'. The retention
settings in the distributor are as follows:

Transaction retention: At least 0 hours and but not more than 72 hours.
History retention: store replication performance History at least 48 hours.

Since we upgrade to SQL 2005 and SQL 2008, I have not encountered this error
for over 2 years as the default is set to 'never expire' I think. So what
happened to my subscription? why all of a sudden, this error comes up. What
is the solution for it?


Any help on this is very much appreciated.

od

--
Message posted via http://www.sqlmonster.com

Quote:
On Thursday, August 12, 2010 11:31 PM Ben Thul wrote:

How do you monitor your replication? Do you know that your subscriber
was not more that 72 hours behind the publisher? If it got outside of
that threshold, that would make the subscription expire, regardless of
settings. Other than that, I cannot think of another reason why that
would happen.
--
Ben
005
ntion
ours.
or
hat
=A0What

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.