Wednesday, March 7, 2012

replication not happening

Since deleting a lot of data from our server, we are having a problem
with one of the (push) merge-replicated servers.
Data was deleted from one table ("Scan" table)
Table has ~ 60 million rows, we deleted in batches, a total of about
3 million rows.
SQL1 is merge replicated with SQL2 (on our LAN in Sydney) and with
SQL3 ( 1Mb link to Melbourne)
Since doing this, (SQL2 is fine) we have had a problem with SQL3.
Symptoms
Agent always shows as running (the small graphic shows the
"play" icon not the "stopped" icon), even after stopping it (although the
context menu correctly shows the relevant start or stop option as expected).
Here are the error details from the Merge agent
<<...OLE_Obj...>>
Attached is the log created by the Merge agent in question.
I did a google on the error, only 1 site hit which suggested the
logging be added to the agen t(which I did, hence the attached verbose log)
otherwise I could find nothing useful.
I have tried changing the Agent profile to use a custom one which
has a query timeout of 1000 (secs) instead of the default 300. No luck.
could you post the results of log output to this newsgroup as opposed to
attaching it. Both the image and the log did not make it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ishan Bhalla" <IshanBhalla@.discussions.microsoft.com> wrote in message
news:3546E77E-1F51-4510-B948-55066A23F7AF@.microsoft.com...
> Since deleting a lot of data from our server, we are having a
problem
> with one of the (push) merge-replicated servers.
> Data was deleted from one table ("Scan" table)
> Table has ~ 60 million rows, we deleted in batches, a total of
about
> 3 million rows.
>
> SQL1 is merge replicated with SQL2 (on our LAN in Sydney) and
with
> SQL3 ( 1Mb link to Melbourne)
> Since doing this, (SQL2 is fine) we have had a problem with SQL3.
>
> Symptoms
> Agent always shows as running (the small graphic shows the
> "play" icon not the "stopped" icon), even after stopping it (although the
> context menu correctly shows the relevant start or stop option as
expected).
> Here are the error details from the Merge agent
> <<...OLE_Obj...>>
>
> Attached is the log created by the Merge agent in question.
> I did a google on the error, only 1 site hit which suggested the
> logging be added to the agen t(which I did, hence the attached verbose
log)
> otherwise I could find nothing useful.
>
> I have tried changing the Agent profile to use a custom one which
> has a query timeout of 1000 (secs) instead of the default 300. No luck.
>

No comments:

Post a Comment