Resources For IT Professionals
Post an article
Wikis - Page Details
Options
RSSSubscribe to Article (RSS)
Can You Improve This Article?
Positively! Click Sign In to add the tip, solution, correction or comment that will help other users.

Report inappropriate content using these instructions.
Wiki  >  TechNet Articles  >  The Ghost in theTransactional Replication Topology

The Ghost in theTransactional Replication Topology

The Ghost in theTransactional Replication Topology

In the course of administering a transactional replication architecture a number of error conditions can occur. Some of these errors are related to synchronization and can be remedied via the issuance of a reinitialization command or stopping and starting the replication agents. Others are not so straightforward and require replication be dropped and recreated. Some still require the publisher database be recreated. This last case are more often the case of ghosts in replication.

These ghosts can occur when OS cluster nodes are out of synch at the block level and one node has an msdb synchronized prior to the removal of a database, or an msdb synchronized for the positive existence of database objects and not the negative, that is to say one way comparison. This is likely a left join of object sets from the active node to the passive node for creation, without the right join of sets for deletion. When the cluster fails over to passive node and the agent, or distributor entry comes into existence after the master has been updated to reflect the removal.



, , [Edit tags]
Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Page 1 of 1 (2 items)