April 26, 2013 at 2:20 pm
Hi Experts
I have added a new publisher to my Publication database but the process is just looping and in status I am seeing this message
The concurrent snapshot for publication 'Databasename_Tables_Pub' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for th
and when I am looking Snapshot agent its looping at [20%] Bulk copied 100000 rows from [dbo].[Table Name] (part 1 of 16) (100000 total rows copied)
Please help
Thanks in Advance.
April 26, 2013 at 3:54 pm
It looks like you have duplicate rows in MSArticles and MSSubscriptions. I would suggest to run the following commands:-
delete distribution..MSarticles where publisher_db = 'YourPublisherDB'
delete distribution..MSsubscriptions where publisher_db = 'YourPublisherDB'
and then setting up replication again.
April 28, 2013 at 10:49 am
What I did I took a backup from Publication server and restored it to Subscription server. The database size match's and everything looks fine but when I build replication the snap shot agent failed to create full snapshot but all the article is showing in publication property's. In this case what are my options. One more question I have as that is what is the best way to delete replication and rebuild it, if you can give me some ideas I will appreciate it. Like which services should be stopped first, is that from distribution side first then the Publication ? and is that OK to delete Snapshot Folder which are old and the old jobs in distribution database.
Thanks a lot for all the help in advance...
April 28, 2013 at 11:23 am
What I did I took a backup from Publication server and restored it to Subscription server. The database size match's and everything looks fine but when I build replication the snap shot agent failed to create full snapshot but all the article is showing in publication property's. In this case what are my options. One more question I have as that is what is the best way to delete replication and rebuild it, if you can give me some ideas I will appreciate it. Like which services should be stopped first, is that from distribution side first then the Publication ? and is that OK to delete Snapshot Folder which are old and the old jobs in distribution database.
Thanks a lot for all the help in advance..
April 28, 2013 at 11:31 am
When you want to setup replication from back up, you do not have to run snapshot agent, because you are already doing the work of snap shot agent by restoring the back up to subscriber.
I would suggest that you drop the publication & subscription and follow the folling steps.
•Set up Publication.
•Set transaction retention to 120 hours for distribution
•Disable the distribution clean up job on the distribution DB
•Setup Publication and set the "allow initalization from backup files" option for the publication
•Make a full backup of the database on the publisher DB
•Restore the full backup on the subscriber DB
•Ran the following stored procedure on the publication database:
-- Run this on publisher DB
sp_addsubscription
@publication ='Publication Name', --Publication Name
@subscriber='servername', --servername of subscriber
@destination_db='SubscriberDB Name', -- Database name where you want to replicate the data
@sync_type = 'initialize with backup',
@backupdevicetype = 'disk',
@backupdevicename = 'Location where the backup was placed' --Location where the back up was placed on subscriber.
go
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply