The subscription(s) have been marked inactive and must be reinitialized.



We have replication set up from our production system to 3 other servers.
MSrepl_commands table on distribution database was filling up as a result
someone tried EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0,
@max_distretention = 0 which deleted all rows from this table . soon after
that replication failed completely and the error shows up as

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

The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.
(Source: DISTRIBUTION (Data source); Error number: 21074). Has anyone seen
thsi error before and if so is there a remedy to this. we had our max
retention set to 336 hrs but since it was forced to run with 0 did it
cleanup data from the distribution database that had to be replicated.
Since its the prodn system any help on this will be greatly appreciated.

TIA

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



Relevant Pages

  • Re: Replication Cleanup in high volume database
    ... We have one subscriber and are using RAID 10 as recommended. ... before moving to SQL 2005 x64, replication was the weak performance link. ... The distribution database has grown to 9GB in < a week. ... * What other parameters can be changed to keep the transactions only as ...
    (microsoft.public.sqlserver.replication)
  • Re: RCVJRNE/exitpgm vs. Mimix
    ... Do you have this in place today from the production system. ... Without having to go for the journal entries and writing exit programs ... journaled and mirrored on a hot-backup system using Mimix product. ... To ensure realtime replication of the data, I would like to use a user ...
    (comp.sys.ibm.as400.misc)
  • Re: Fault tolerant distributor in merge replication and data mirroring (in SQL Server 2005/2008)
    ... but it's quite expensive and my customer doesn't ... When I said fault-tolerant I didn't mean "real time recovery", ... As it's a Merge Replication there can be this small downtime, ... tolerant system for the distribution database? ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication general question
    ... I know it is used in BOL and in a lot of other places. ... refuse to ever implement replication again, because "it doesn't work" or "I ... is on one server, part of the data on another server, and part of the data ... distribution database from server 2 and no agent in the system has the ...
    (microsoft.public.sqlserver.replication)
  • Re: General SQL Server 2005 transactional replication question
    ... Looking for a SQL Server replication book? ... presumably all my changes to that database are relayed to ... in the distribution database until it comes back up? ...
    (microsoft.public.sqlserver.replication)