Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

View Synchronization Status Error Expand / Collapse
Author
Message
Posted Friday, April 26, 2013 2:20 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 9:16 AM
Points: 52, Visits: 817
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.


  Post Attachments 
Replication Error.JPG (2 views, 69.77 KB)
Post #1447153
Posted Friday, April 26, 2013 3:54 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 8:40 AM
Points: 832, Visits: 1,178
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.
Post #1447187
Posted Sunday, April 28, 2013 10:49 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 9:16 AM
Points: 52, Visits: 817
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...
Post #1447334
Posted Sunday, April 28, 2013 11:23 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 9:16 AM
Points: 52, Visits: 817

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..
Post #1447339
Posted Sunday, April 28, 2013 11:31 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 8:40 AM
Points: 832, Visits: 1,178
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
Post #1447340
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse