Showing posts with label server1. Show all posts
Showing posts with label server1. Show all posts

Saturday, 25 February 2012

Conflicts how can it be possible

Dear Friends
I am getting the conflict for the records with following
remark.
The row was updated at 'SERVER1.DATABASE1' but could not
be updated at 'SERVER2.DATABASE2'. Violation of PRIMARY
KEY constraint 'PK__TABLE04__5DF6A344'. Cannot insert
duplicate key in object 'TABLE04'.
This record is created in SERVER2 AND ALSO CHANGED IN
SERVER2. The replication was down and then it come up
with this error when the user have change on same record.
Can you please suggest what can be the reason.
Publisher have not change anything every change is done
by the supplier still it is in the conflict.
Your guidance will help me a lot.
Best regards
Sharad
Is it possible that you updated the primary key? This might cause this
problem.
You also might want to edit your update proc and comment out the section
where it updates the pk in the second portion of the update proc.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Sharad" <niitmalad@.yahoo.co.in> wrote in message
news:06f901c4ec1e$5ed33310$a501280a@.phx.gbl...
> Dear Friends
> I am getting the conflict for the records with following
> remark.
> The row was updated at 'SERVER1.DATABASE1' but could not
> be updated at 'SERVER2.DATABASE2'. Violation of PRIMARY
> KEY constraint 'PK__TABLE04__5DF6A344'. Cannot insert
> duplicate key in object 'TABLE04'.
> This record is created in SERVER2 AND ALSO CHANGED IN
> SERVER2. The replication was down and then it come up
> with this error when the user have change on same record.
> Can you please suggest what can be the reason.
> Publisher have not change anything every change is done
> by the supplier still it is in the conflict.
> Your guidance will help me a lot.
> Best regards
> Sharad

Friday, 24 February 2012

conflict Problem Help

Hello Everybody
I am having merge Replication using MSSQL 2000 sp3 latest security patch,
My replication is server1 Publisher, server2 subscriber, server3
subscriber,
Server4 subscriber, server5 subscriber. I am using schedule around 1:00
AM every day, In Server2 we insert 5 rows some value, and 5 rows sending to
Server3 using DTS with Insert statement, and server3 we update the 5Rows,
and sending to Server4 or server2, this all process everything done before
synchronize. I am using default conflict revolver, becoz some table dont
have date time field. When I run the merge agent, I got some conflict in
conflict tables. Automatically delete some row in subscriber.
How to resolve those problems. I need urgent help.
The same row was updated at 'THSWPSW002.GCP' and deleted at
'BKKNTS370.GCPTEST'.
The resolver chose the deletion as the winner.
3:3 conflict_type : reason_code
The same column(s) of the same row was updated at both 'SERVER1.APPTEST' and
' SERVER2.APPTEST '.
The resolver chose the update from ' SERVER1.APPTEST ' as the winner.
2:2
The row was inserted at ' SERVER5.APPTEST ' but could not be inserted at '
SERVER1.APPTEST '. Violation of PRIMARY KEY constraint
'PK__T_M_SUPPLIER__3607E224'. Cannot insert duplicate key in object
'T_M_SUPPLIER'.
5:2627
The row was inserted at 'SERVER1.APPTEST' but could not be inserted at
'SERVER2.APPTEST'. Violation of PRIMARY KEY constraint
'PK__T_M_SUPPLIER__38CF4036'. Cannot insert duplicate key in object
'T_M_SUPPLIER'.
6:2627
The same row was updated at both 'SERVER1.APPTEST' and 'SERVER5.APPTEST'.
The resolver chose the update from 'BKKNTS370.GCPTEST' as the winner.
1:1
Thanks
Sam
Sam,
please take a look at this article and see if it applies:
http://support.microsoft.com/default...&Product=sql2k
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks,
Still i have problem some conflict.
i change mergearticle error 'flase'
could you tell me how to handule ?
Sam
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ui2754ILGHA.2276@.TK2MSFTNGP15.phx.gbl...
> Sam,
> please take a look at this article and see if it applies:
> http://support.microsoft.com/default...&Product=sql2k
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>