Due to network failure (2 hours a day) replication fails between the servers. Normally when network is down for more than an hr, I am not able to restart the replication process by starting the agent. All RED cross marks Appears in the runing services.
Please tell me how do I manage this condition using some frontend deamon that check the replication status, if the replication is down due to network prob or any other reason, daemon tries to restart the replication process.
From http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
Schedule your agents to restart every 5 minutes. If an agent fails it will
fail for a specific reason. The most common reasons are network
interruptions.
I would poll the msrepl_errors table on the distribution database and have
new errors sent to me via a page. I could then evaluate whether the
automatic scheduled restart will clear the error condition.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Madhur" <raj_max@.hotmail.com> wrote in message
news:6a88e5f5-42b0-4969-99cc-c41781493419@.developmentnow.com...
> Due to network failure (2 hours a day) replication fails between the
> servers. Normally when network is down for more than an hr, I am not able
> to restart the replication process by starting the agent. All RED cross
> marks Appears in the runing services.
> Please tell me how do I manage this condition using some frontend deamon
> that check the replication status, if the replication is down due to
> network prob or any other reason, daemon tries to restart the replication
> process.
> From
> http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts
Tuesday, March 20, 2012
Saturday, February 25, 2012
Replication keeps failing after one failure
Hi,
We are running Merge Replication on Sql Server 2K with multiples MSDE 2K subsciber.The Replication is getting done through a Visual Basic Application and it works fine as long as it does not fail.Once the replication fails on the Clients machine then we always need to blow the Local Database on the Client's machine and then start the Merge Replication process again.I wonder Why?Any help is really appriciated.. :(It's necessary adjust the retry count for the merge agent, in the event it fails (e.g. remote computer is turned off, network failure etc.). Expand Replication monitor, expand agents, click on merge agents. A list of merge agents, corresponding to each location is listed on the right. To change retry count for a merge agent, highlight the merge agent, right click and select agent properties. Click on tab "Steps", Highlight ID 2 (step 2 - run agent), click on edit. Step name should say "Run agent". Click on Advanced tab, and adjust the retry count and retry interval.
:D|||Thanks for your reply and I will increase the Number of Retry but my question is still unanswered and that's Why the Replication keeps failing after one failure?Is this turning on some flag somewhere in the Sql Server after a failure?|||Ok, I'm confused.
Replication is done via a Visual Basic program?
Replication is a configuration of Sql Server. Has nothing to do with Visual Basic.
What kind of Merge replication is setup? Merge continuosly, or scheduled merge?
If Merge continuously, then the retry count and schedule HAS to be changed. The defaults will cause the agent to fail if the connection is down for just 10 minutes. (10 retries, at 1 minute intervals).
Also, when you say replication fails, there are error messages that can be viewed via replication monitor. The agent may try 10 times, and on failure display 1 message. That doesn't mean there were no retries.|||It's a Merge Replication which runs on Demand through Visual Basic Application.The process works fine 9/10 times but if its fails then it keeps failing and the error log says "The Process was Successfully Stopped".I also don't think that it involves any network issue as the subscriber is connected to the network all the time.
Also once the Synchronization fails then we need to set the Initial database at the subscriber(which involves defining the subscriber,creating the local DB,Copying Roles and creating a dynamic Merge Replication job) and then do the Regular Synchronization,which works fine thereafter.
I don't know Y?:confused:
We are running Merge Replication on Sql Server 2K with multiples MSDE 2K subsciber.The Replication is getting done through a Visual Basic Application and it works fine as long as it does not fail.Once the replication fails on the Clients machine then we always need to blow the Local Database on the Client's machine and then start the Merge Replication process again.I wonder Why?Any help is really appriciated.. :(It's necessary adjust the retry count for the merge agent, in the event it fails (e.g. remote computer is turned off, network failure etc.). Expand Replication monitor, expand agents, click on merge agents. A list of merge agents, corresponding to each location is listed on the right. To change retry count for a merge agent, highlight the merge agent, right click and select agent properties. Click on tab "Steps", Highlight ID 2 (step 2 - run agent), click on edit. Step name should say "Run agent". Click on Advanced tab, and adjust the retry count and retry interval.
:D|||Thanks for your reply and I will increase the Number of Retry but my question is still unanswered and that's Why the Replication keeps failing after one failure?Is this turning on some flag somewhere in the Sql Server after a failure?|||Ok, I'm confused.
Replication is done via a Visual Basic program?
Replication is a configuration of Sql Server. Has nothing to do with Visual Basic.
What kind of Merge replication is setup? Merge continuosly, or scheduled merge?
If Merge continuously, then the retry count and schedule HAS to be changed. The defaults will cause the agent to fail if the connection is down for just 10 minutes. (10 retries, at 1 minute intervals).
Also, when you say replication fails, there are error messages that can be viewed via replication monitor. The agent may try 10 times, and on failure display 1 message. That doesn't mean there were no retries.|||It's a Merge Replication which runs on Demand through Visual Basic Application.The process works fine 9/10 times but if its fails then it keeps failing and the error log says "The Process was Successfully Stopped".I also don't think that it involves any network issue as the subscriber is connected to the network all the time.
Also once the Synchronization fails then we need to set the Initial database at the subscriber(which involves defining the subscriber,creating the local DB,Copying Roles and creating a dynamic Merge Replication job) and then do the Regular Synchronization,which works fine thereafter.
I don't know Y?:confused:
replication job failure
Our SQl Server 2000 was rebooted recently but when I check the management
section then jobs replication its registered as failed yet when checking the
history it is still executing step 2.
Yet when I check in the replication monitor in the distribution agents
replication is as normal do you know how I can get rid of the fail status if
it is still processing transaction replication that has been running for 3
days on step 2?
thanks for any help
Sammy
Sammy,
you could try stopping and restarting the job, then refresh.
Rgds,
Paul Ibison
|||Thanks Paul it worked
"Paul Ibison" wrote:
> Sammy,
> you could try stopping and restarting the job, then refresh.
> Rgds,
> Paul Ibison
>
>
section then jobs replication its registered as failed yet when checking the
history it is still executing step 2.
Yet when I check in the replication monitor in the distribution agents
replication is as normal do you know how I can get rid of the fail status if
it is still processing transaction replication that has been running for 3
days on step 2?
thanks for any help
Sammy
Sammy,
you could try stopping and restarting the job, then refresh.
Rgds,
Paul Ibison
|||Thanks Paul it worked
"Paul Ibison" wrote:
> Sammy,
> you could try stopping and restarting the job, then refresh.
> Rgds,
> Paul Ibison
>
>
Subscribe to:
Posts (Atom)