Post reply

Replication vanished

  • March 25, 2007 at 9:49 am

    #173024

    Hi,

    Here is a situation my friend found in a production environment..

    They have a Sql Sever 2000 with couple of databases and the server was configured with snapshot and merge replications. As the databases were small, the same server is used as publisher as well as distributor

    yesterday there was a long datacenter power outage and they had to shutdown the sqlservers

    when the outage was resolved and sql servers were started all the other servers were fine but on the server with replication was configured, the distribution database was missing.. not sure what to do, he tried restoring the backup of that database which was taken before shutting down the server but still nothing shows up in it.

    What can be done to resolve this other than setting up the replication again from scratch?

    Thanks in advance

    Phani

     

     

  • March 25, 2007 at 10:56 pm

    #696804

    well there are couple of things that could be done in this scenario

    1. Check if the SQL Server error logs show any errors pertaining to the distribution agent

    2. try to restore your Distribution database

    3. check syspubliclication if any publication exits or not

    4. Or you might have to restablish replication if nothing works

    but before you plan to restalish replication

    execute sp_removedbreplication <db name> on subscriber first

    next distributor next publisher

    - Krishna

  • March 26, 2007 at 7:40 am

    #696868

    Thanks for the reply Krishna,

    Error logs does not have any information

    he tried restoring the distribution database but it does not contain any valid info.

    I will ask him to check syspublications

  • March 27, 2007 at 1:26 am

    #697058

    There is a system job to clean up subscription if inactive which could have cleaned up this. You can trace this part of the job history .

    There is no short-cut for restoring the replication in this situation other than to use one of the available databases and see which one can choose .. depending upon which one is most recent as compared to the other or other  unique issues to your production environment and start setting up the replication from the beginning.

    Once the replication is setup, Make sure you disable the system job for cleaning up the subscription, so that you don't face this problem again

    rangark.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply