Showing posts with label continuous. Show all posts
Showing posts with label continuous. Show all posts

Friday, March 23, 2012

Merge Replication stopping

Hi,
We have Merge Continuous replication. Every couple of days the Merge
agent stops with an error:
The process could not enumerate changes at the 'Publisher'. Source:
Merge Replication Provider (Agent); Error number: -2147200999
We are running on SQL2000 Standard, SP4. The OS is Windows 2000 Server
SP4
Has anyone seen this?
Thanks,
Katrin
Yep. The merge agent (replmerg.exe) was either excessively blocked or
deadlocked with another process. How many rows do you have in your
MSmerge_contents and MSmerge_genhistory tables on both publisher and
subscriber?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"katrin" <katrinkump@.gmail.com> wrote in message
news:1143825489.438770.13630@.i39g2000cwa.googlegro ups.com...
> Hi,
> We have Merge Continuous replication. Every couple of days the Merge
> agent stops with an error:
> The process could not enumerate changes at the 'Publisher'. Source:
> Merge Replication Provider (Agent); Error number: -2147200999
> We are running on SQL2000 Standard, SP4. The OS is Windows 2000 Server
> SP4
> Has anyone seen this?
>
> Thanks,
> Katrin
>

Merge Replication stopping

Hi,
We have Merge Continuous replication. Every couple of days the Merge
agent stops with an error:
The process could not enumerate changes at the 'Publisher'. Source:
Merge Replication Provider (Agent); Error number: -2147200999
We are running on SQL2000 Standard, SP4. The OS is Windows 2000 Server
SP4
Has anyone seen this?
Thanks,
Katrin
normally this error is transitory and will go away on subsequent syncs. If
it does not enable logging to determine if there is another error which is
masked by this error.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<katrinkump@.gmail.com> wrote in message
news:1143825341.447084.133130@.j33g2000cwa.googlegr oups.com...
> Hi,
> We have Merge Continuous replication. Every couple of days the Merge
> agent stops with an error:
> The process could not enumerate changes at the 'Publisher'. Source:
> Merge Replication Provider (Agent); Error number: -2147200999
> We are running on SQL2000 Standard, SP4. The OS is Windows 2000 Server
> SP4
> Has anyone seen this?
>
> Thanks,
> Katrin
>

Merge replication stopping

Hi All,
I have selected merge replication because both servers are constantly
updating information. We have continuous merge replication (push) and
everything works pretty good.
The problem is in some occassions the job stops saying that it can not
enumerate the changes on the subscriber, if I restart it works fine. This is
causing more than a headache because we always have to be watching if
replication is working. I try to change the job to restart when it fails but
it doesn't work.
I have one publisher with the distributor on the same machine pushing the
continuous merge to one subscriber.
Can this happen because the subscriber is busy and the job can connect? Have
anyone seen this happening?
Thanks a lot
Yes, it is typically a transitory error. Many dba's run their merge agents
in infinite loops by having step 3 looping back to step 1.
Hilary Cotter
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
"Salvador" <Salvador@.discussions.microsoft.com> wrote in message
news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@.microsoft.com...
> Hi All,
> I have selected merge replication because both servers are constantly
> updating information. We have continuous merge replication (push) and
> everything works pretty good.
> The problem is in some occassions the job stops saying that it can not
> enumerate the changes on the subscriber, if I restart it works fine. This
is
> causing more than a headache because we always have to be watching if
> replication is working. I try to change the job to restart when it fails
but
> it doesn't work.
> I have one publisher with the distributor on the same machine pushing the
> continuous merge to one subscriber.
> Can this happen because the subscriber is busy and the job can connect?
Have
> anyone seen this happening?
> Thanks a lot
|||We have the job running every minute and it seems to work fine. I have
noticed that the retry doesn't work like one would think it should.
If you go to Merge Agent History, Session Details, Error Details, you should
get more information on why it can't continue. We get a lot of deadlocks
causing the agent to fail, but when it picks back up a minute later it
usually works fine.
Dylan Peters
"Hilary Cotter" wrote:

> Yes, it is typically a transitory error. Many dba's run their merge agents
> in infinite loops by having step 3 looping back to step 1.
> --
> Hilary Cotter
> 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
> "Salvador" <Salvador@.discussions.microsoft.com> wrote in message
> news:723F7F3D-6BE0-4205-B79F-01CA227E7EF7@.microsoft.com...
> is
> but
> Have
>
>
sql

Monday, March 12, 2012

Merge Replication limit running in continuous mode

Hi,
We have a customer site running merge replication with a
publisher/distributer and 12 subscribers. All the merge agents are running in
continuous mode. It seems that two of the agents are always failed, or don't
last long. Is this directly related to the "number of concurrent merge
processes" number? It looks like because there are 10 merge agents *always*
running, the other two don't get a look in. Is this correct?
We can increase this number to 20 and the site seems to run ok, but we've
been hearing rumours that any number past 10 concurrent merge processes gets
unstable. What's the MS position on this?
What's the recommended solution to this situation? Schedule the agents
instead of continuous mode?
What is the error message generated by these two always failing agents?
Do you have the "limit the number of concurrent merge processes to the
following" option checked and set to 10.
What happens is that for long running merge agents the agents will timeout
or deadlock themselves, so MS advised you to limit the number that run
concurrently.
If you do choose this option you have to configure your agents to wait a
longer time before timing out. To do this right click on your merge agents,
select agent properties, click on the Steps tab, and double click on Run
Agent. Place focus in the commands text box, press End, and press the space
bar. enter -StartQueueTimeout 120
This will have the effect of having these two failing merge agents of
waiting up to 2 minutes for the first 10 merge agents in the queue to finish
their work.
I am not sure what the rational for 10 was. The fact it seems to work fine
when you bump it up to 20 seems to indicate that this throttling is not
optimal for you. I suspect that you did not use StartQueueTimeout option.
Running the agents in continuous mode will have no effect. The agents poll
by default every minute, so after the agent completes it will go to sleep
for a minute, and any agents in the queue will have their timeslice.
Hilary Cotter
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
"Sydney" <hsc@.newsgroup.nospam> wrote in message
news:5C49D704-C649-41FA-8686-3EA92151867F@.microsoft.com...
> Hi,
> We have a customer site running merge replication with a
> publisher/distributer and 12 subscribers. All the merge agents are running
> in
> continuous mode. It seems that two of the agents are always failed, or
> don't
> last long. Is this directly related to the "number of concurrent merge
> processes" number? It looks like because there are 10 merge agents
> *always*
> running, the other two don't get a look in. Is this correct?
> We can increase this number to 20 and the site seems to run ok, but we've
> been hearing rumours that any number past 10 concurrent merge processes
> gets
> unstable. What's the MS position on this?
> What's the recommended solution to this situation? Schedule the agents
> instead of continuous mode?
>

Wednesday, March 7, 2012

Merge replication delay

Hi,Friends
We have found a merge replication in two domain with one anonimous
subscriber. And we set the continuous replication. But the problem is that
data changed on publisher can not replicate immediately to subscriber.
Sometimes after 3 or 4 hours, sometimes after two days.
And in history logs there is a message occured frequently :
waiting for a background application call ( for excution, i can not remember
clearly )
Help me pls!
Thanks
Set your merge to use longer intervals - e.g. 15 minutes
After each sync check for data conflicts at the PUBLISHER side and check for
any other errors
The 15 minute gap will allow you time to see what exactly is going on
"Titanicliu" wrote:

> Hi,Friends
> We have found a merge replication in two domain with one anonimous
> subscriber. And we set the continuous replication. But the problem is that
> data changed on publisher can not replicate immediately to subscriber.
> Sometimes after 3 or 4 hours, sometimes after two days.
> And in history logs there is a message occured frequently :
> waiting for a background application call ( for excution, i can not remember
> clearly )
> Help me pls!
> Thanks