|
|
You're in the
sql server replication
group:The merge process failed
sql server replication:
hi, i have been playing around with the custom resolver for merge
replication. i have a merge publication with 1 article having non overlapping partitions dynamic partitions going to a single partition. i have 2 subscriptions which had row tracking enabled. i changed the resolver to microsoft sqlserver averaging conflict resolver and the tracking to column tracking. After reinitializing the subscriptions one subscription worked fine while the other gave the following error "The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3." i even tried to create a new snapshot for that partition and then reinitialize the subscription but what happens is that it applies the snapshot succesfully to the subscriber in the next synchronization but afterwards the same error message appears. i can re-create the subscription since this is on a test database but i want to find out why this error is coming so i would be nice if you could help solve this without dropping the subscription thanks
same error occurs even if i change the resolver
[quoted text, click to view] Hilary Cotter wrote:
> It sounds like your custom resolver is breaking your subscription. Do you > get this error if you use a different resolver? > > -- > 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 > > > > "Udit Ghai" <ghai.udit@gmail.com> wrote in message > news:1161930941.106320.291430@f16g2000cwb.googlegroups.com... > > hi, i have been playing around with the custom resolver for merge > > replication. i have a merge publication with 1 article having non > > overlapping partitions dynamic partitions going to a single partition. > > i have 2 subscriptions which had row tracking enabled. i changed the > > resolver to microsoft sqlserver averaging conflict resolver and the > > tracking to column tracking. After reinitializing the subscriptions one > > subscription worked fine while the other gave the following error > > > > "The merge process failed because it detected a mismatch between the > > replication metadata of the two replicas, such that some changes could > > be lost leading to non-convergence. This could be due to the subscriber > > not having synchronized within the retention period, or because of one > > of the replicas being restored to a backup older than retention period, > > or because of the publisher performing more aggressive cleanup on > > articles of type download-only and articles with partition_options = > > 3." > > > > i even tried to create a new snapshot for that partition and then > > reinitialize the subscription but what happens is that it applies the > > snapshot succesfully to the subscriber in the next synchronization but > > afterwards the same error message appears. i can re-create the > > subscription since this is on a test database but i want to find out > > why this error is coming so i would be nice if you could help solve > > this without dropping the subscription > > > > thanks > >
It sounds like your custom resolver is breaking your subscription. Do you
get this error if you use a different resolver? -- 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 [quoted text, click to view] "Udit Ghai" <ghai.udit@gmail.com> wrote in message news:1161930941.106320.291430@f16g2000cwb.googlegroups.com... > hi, i have been playing around with the custom resolver for merge > replication. i have a merge publication with 1 article having non > overlapping partitions dynamic partitions going to a single partition. > i have 2 subscriptions which had row tracking enabled. i changed the > resolver to microsoft sqlserver averaging conflict resolver and the > tracking to column tracking. After reinitializing the subscriptions one > subscription worked fine while the other gave the following error > > "The merge process failed because it detected a mismatch between the > replication metadata of the two replicas, such that some changes could > be lost leading to non-convergence. This could be due to the subscriber > not having synchronized within the retention period, or because of one > of the replicas being restored to a backup older than retention period, > or because of the publisher performing more aggressive cleanup on > articles of type download-only and articles with partition_options = > 3." > > i even tried to create a new snapshot for that partition and then > reinitialize the subscription but what happens is that it applies the > snapshot succesfully to the subscriber in the next synchronization but > afterwards the same error message appears. i can re-create the > subscription since this is on a test database but i want to find out > why this error is coming so i would be nice if you could help solve > this without dropping the subscription > > thanks >
Could you post the schema of the problem table here?
-- 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 [quoted text, click to view] "Udit Ghai" <ghai.udit@gmail.com> wrote in message news:1161955921.012391.244850@h48g2000cwc.googlegroups.com... > same error occurs even if i change the resolver > > Hilary Cotter wrote: > >> It sounds like your custom resolver is breaking your subscription. Do you >> get this error if you use a different resolver? >> >> -- >> 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 >> >> >> >> "Udit Ghai" <ghai.udit@gmail.com> wrote in message >> news:1161930941.106320.291430@f16g2000cwb.googlegroups.com... >> > hi, i have been playing around with the custom resolver for merge >> > replication. i have a merge publication with 1 article having non >> > overlapping partitions dynamic partitions going to a single partition. >> > i have 2 subscriptions which had row tracking enabled. i changed the >> > resolver to microsoft sqlserver averaging conflict resolver and the >> > tracking to column tracking. After reinitializing the subscriptions one >> > subscription worked fine while the other gave the following error >> > >> > "The merge process failed because it detected a mismatch between the >> > replication metadata of the two replicas, such that some changes could >> > be lost leading to non-convergence. This could be due to the subscriber >> > not having synchronized within the retention period, or because of one >> > of the replicas being restored to a backup older than retention period, >> > or because of the publisher performing more aggressive cleanup on >> > articles of type download-only and articles with partition_options = >> > 3." >> > >> > i even tried to create a new snapshot for that partition and then >> > reinitialize the subscription but what happens is that it applies the >> > snapshot succesfully to the subscriber in the next synchronization but >> > afterwards the same error message appears. i can re-create the >> > subscription since this is on a test database but i want to find out >> > why this error is coming so i would be nice if you could help solve >> > this without dropping the subscription >> > >> > thanks >> > >
CREATE TABLE [dbo].[Country](
[CountryID] [tinyint] NOT NULL, [Country] [nchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [SalesAmount] [money] NULL, [ProfitMargin] [tinyint] NULL, [Emp#] [smallint] NULL, [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_B389D91DC4AB4995AF7890432D74DA55] DEFAULT (newsequentialid()), CONSTRAINT [PK_Country] PRIMARY KEY CLUSTERED ( [CountryID] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] [quoted text, click to view] Hilary Cotter wrote:
> Could you post the schema of the problem table here? > > -- > 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 > > > > "Udit Ghai" <ghai.udit@gmail.com> wrote in message > news:1161955921.012391.244850@h48g2000cwc.googlegroups.com... > > same error occurs even if i change the resolver > > > > Hilary Cotter wrote: > > > >> It sounds like your custom resolver is breaking your subscription. Do you > >> get this error if you use a different resolver? > >> > >> -- > >> 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 > >> > >> > >> > >> "Udit Ghai" <ghai.udit@gmail.com> wrote in message > >> news:1161930941.106320.291430@f16g2000cwb.googlegroups.com... > >> > hi, i have been playing around with the custom resolver for merge > >> > replication. i have a merge publication with 1 article having non > >> > overlapping partitions dynamic partitions going to a single partition. > >> > i have 2 subscriptions which had row tracking enabled. i changed the > >> > resolver to microsoft sqlserver averaging conflict resolver and the > >> > tracking to column tracking. After reinitializing the subscriptions one > >> > subscription worked fine while the other gave the following error > >> > > >> > "The merge process failed because it detected a mismatch between the > >> > replication metadata of the two replicas, such that some changes could > >> > be lost leading to non-convergence. This could be due to the subscriber > >> > not having synchronized within the retention period, or because of one > >> > of the replicas being restored to a backup older than retention period, > >> > or because of the publisher performing more aggressive cleanup on > >> > articles of type download-only and articles with partition_options = > >> > 3." > >> > > >> > i even tried to create a new snapshot for that partition and then > >> > reinitialize the subscription but what happens is that it applies the > >> > snapshot succesfully to the subscriber in the next synchronization but > >> > afterwards the same error message appears. i can re-create the > >> > subscription since this is on a test database but i want to find out > >> > why this error is coming so i would be nice if you could help solve > >> > this without dropping the subscription > >> > > >> > thanks > >> > > >
hey some help required over here
thanks,
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |