The subscription(s) have been marked inactive.....

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 7,2000 » Replication » The subscription(s) have been marked...

21 posts, Page 2 of 3

««1 2 3 »»

The subscription(s) have been marked inactive.....

Rate Topic

Display Mode

Topic Options

Author

Message

ShekharNaidu

Posted Monday, June 26, 2006 2:10 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 08, 2010 10:45 PM
Points: 122, Visits: 70

Thank you for replies...

I will try those suggestions..

Shekhar

Thanks ,

Shekhar

Post #290016

ShekharNaidu

Posted Tuesday, September 26, 2006 1:17 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 08, 2010 10:45 PM
Points: 122, Visits: 70

Andrew,

Can you please tell me the job name which is monitoring the subscribers expiration..

Thank You

Chandra Shekar

Thanks ,

Shekhar

Post #311146

Brad Scheepers

Posted Thursday, September 18, 2008 2:06 AM

Valued Member

Group: General Forum Members
Last Login: Thursday, February 21, 2013 3:18 AM
Points: 57, Visits: 214

Hi guys ...

When it says the snapshot has been marked as inactive, it's because the snapshot needs to run on it's own schedule in the background (and seems to ignore that it is marked as never expiring).

So check the schedule of the snapshot agent and let it run something like once a week on a Sunday morning for example. You may still have to reinitialise the publication to get it all sorted out again.

Post #571540

Wired-528862

Posted Friday, May 08, 2009 4:27 PM

Forum Newbie

Group: General Forum Members
Last Login: Friday, September 03, 2010 3:29 PM
Points: 8, Visits: 48

Brad Scheepers (9/18/2008)

Can you expand on this more. I'm new to replication and I'm not sure where to check the Snapshot agent schedule. Thanks.

Post #713412

sunrise.freedom

Posted Tuesday, October 20, 2009 2:04 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, January 07, 2010 8:33 AM
Points: 1, Visits: 15

Hi guy,
just run this query in a new query window in the distribution server Smile

USE distribution

Update [MSsubscriptions]
Set [status] = 2

Post #806071

Wired-528862

Posted Tuesday, October 20, 2009 2:09 PM

Forum Newbie

Group: General Forum Members
Last Login: Friday, September 03, 2010 3:29 PM
Points: 8, Visits: 48

^^^Thanks for the script.

FYI- I did more research and found that it appears the subscriptions will be marked inactive if nothing is replicated in 48 hours. To resolve this, I have an update script running every 12 hours that updates a users lock status to unlocked or something similar. Just update something that's replicated and so far I have not had any subscriptions marked as inactive for a few weeks now. Hope this helps.

Post #806076

dsusca

Posted Monday, July 26, 2010 11:34 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, July 18, 2011 1:06 PM
Points: 1, Visits: 56

Tanks for this script Smile

Post #958947

bbalub

Posted Wednesday, November 24, 2010 3:47 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, October 29, 2012 4:58 AM
Points: 3, Visits: 208

Threre are many reasons when a subscriptions becomes inactive. I too got into similar situation. Microsoft says

"If a subscription is not synchronized within the maximum distribution retention period (default of 72 hours) and there are changes in the distribution database that have not been delivered to the Subscriber, the subscription will be marked deactivated by the Distribution clean up job that runs on the Distributor. The subscription must be reinitialized."

This means that if you have some changes in the distributor that has to be propagated to the Subscriber and if that retention period exceeds the maximum retention period 72 hours by default, then the job Distribution clean up will make your subscriptions inactive. You can configure this retention period through right click Replication -> Configure Distributor -> Retention Period

Post #1025763

sqldba.avinash

Posted Tuesday, October 11, 2011 11:49 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, October 11, 2011 11:48 AM
Points: 1, Visits: 0

Whenever there is an error as mentioned above then, you can try to update the status column in the MSsubscriptions table in the distribution database. The status column for the expired subscription indicated a value of 0 meaning inactive. The value of 2 in the status column means Active.

Try the following steps:
1. Select * from MSsubscriptions to locate the expired subscription.
2. Use the query below to reset the status in MSsubscriptions table. Fill in the values for the publisher_id, publisher_db, publication_id, subscriber_id and subscriber_db in the query below with the values from the expired subscription in the MSsubscriptions table.

update distribution..MSsubscriptions set status=2 where publisher_id='x' andpublisher_db='x' and publication_id='x' and subscriber_id='x' and subscriber_db='x'

Status of the subscription:
0 = Inactive
1 = Subscribed
2 = Active

This steps wil give you the solution to above problem, i fixed it through the following steps only

Avinash

Post #1188645

Barry Jones-426846

Posted Friday, June 15, 2012 12:16 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, February 20, 2013 8:00 PM
Points: 7, Visits: 32

If you don't watch the errors (or the alert fails in our case) for a few days then the subscription will be marked inactive.
Issues with the login account used will prevent a subscription from being active. It will simply fail to log on.

Also, if it has been inactive for a while then the subscriber will be out of sync - as in the case with updatable transactional subscriptions.

Finding the cause of the inactivity is best viewed from the Job history, not replication monitor (which says it is inactive, not why). Find the job, check the history out to identify the cause.

Resolution steps...
1. Stop the job. (or all replication jobs for the database (including from other publications eg 2 way upd...trans...repln))

2. Apply fix: Change the subscription properties to use a different account (if this was the cause).

3. Apply workaround: Use the preferred update script or sp mentioned before to set the status = 2 (applies to each articles in the publication) in MSsubscription

4. Restart the job. Watch the Job Activity as well to make sure it is running OK. If not, find the cause, repeat steps.

If you are still getting a failure caused by undistributed transactions failing to get through then you may have to clear the MSrepln_commands and manually sync changes using RedGate SQLCompare before restarting the job.

Simply reinitialising a subscription isn't always practical when the publication database is over 20Gb, the subscriber has a crap connection on the other side of the world and has only a small maintenance window to get the job done.

Good luck.

Post #1316829

« Prev Topic | Next Topic »

21 posts, Page 2 of 3

««1 2 3 »»

Permissions