November 13, 2009 at 1:59 am
Hi,
I need some help with SQL 2000 Replication erroring...
We have 3 servers each located in separate countries. One of these three servers has just (this week) started having the error "The process could not log conflict information" logged. Each server has a publication database, but also has a subscription database from the other two servers (push merge subscriptions. We also have a secons server in the same office as the one failing with a copy of all 3 on too.
Yesterday I rebuilt the replication for the failing server and it rebuilt fine but then started failing next time a conflict occurred.
The only two things I can see that are different about this one server are that it hosts the largest of the three databases. Also as it is so large, I have created two separate publications on the db otherwise it is too big to distribute to the subscribers and often fails before completing the snapshot rollout - due to the slow WAN links which are fast enough for normal replication but slow for a roll-out.
I have seen MS Article ID: 927186 but I do not beleive this relates to the error we have (I may be wrong).
All four servers are running SQL 2000 SP4 (8.00.2055)
The error is below...
Last Command
{call [sp_cft_2B6D574BBEDD46FD1D684343E6B44B13] ( ? , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ,? ,? ,? ,?)}
Error Message
The process could not log conflict information.
Error Details
The process could not log conflict information.
(Source: Merge Replication Provider (Agent); Error number: -2147200992)
---------------------------------------------------------------------------------------------------------------
Implicit conversion from data type datetime to tinyint is not allowed. Use the CONVERT function to run this query.
(Source: SQL-UK2 (Data source); Error number: 257)
---------------------------------------------------------------------------------------------------------------
I hope someone call help me please...
November 26, 2009 at 8:49 am
Hi,
I'm not quite sure of your set up..
3 servers..all with published data bases...are they all publishing to each other ??
Thanks
Graeme
November 26, 2009 at 9:06 am
Hi Graeme,
What I meant to say was there are 3 databases in total. Each one called UK, US or HK.
Server "SQL-UK1" has 3 databases
UK (published from here)
US
HK
Server "SQL-UK2" has 3 databases
UK
US
HK
Server "SQL-HK" has 3 databases
UK
US
HK (published from here)
Server "SQL-US" has 3 databases
UK
US (published from here)
HK
All were fine but now the replication keeps coming up with this cannot log conflict error. I have tried completely removing replication from publication and subscriber dbs, etc. and rebuilding. No luck!
Any ideas?
Steve
November 26, 2009 at 9:44 am
This error from your original post
Implicit conversion from data type datetime to tinyint is not allowed. Use the CONVERT function to run this query.
(Source: SQL-UK2 (Data source); Error number: 257)
Would suggest that the conflict tables may be the wrong structure.
Have you had a structural change at all ?
Graeme
November 26, 2009 at 10:06 am
Hi Graeme,
Yes, we have changed things but we do occassionally add or drop columns as appropriate using the sp_repladdcolumn. As mentioned, I have completely rebuilt (about 5-6 times) and re snapshotted (adfter removig all elements of the replication in the dbs). The snapshot application works, it is when a change is replicated it fails.
The other two dbs are almost identical but are not failing (they have not been rebuild for a month or so though).
In fact one of the dbs that is still working also has more columns than this failing db.
Thanks Steve
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy