all groups > sql server replication > march 2005 >
You're in the sql server replication group:
Merge-Agent error
sql server replication:
Hi, the Merge-Agent stops with the following error: The merge process couldn't recall the information for the table 'xxx' What is the reasen for the problem ? What can I do ? Best regards
Sorry I made a mistake, the right error message is: The mergeprocess coundn't recall the column information for the table 'XXX' Best regards Axel Lanser [quoted text, click to view] "ALN" wrote: > Hi, > the Merge-Agent stops with the following error: > > The merge process couldn't recall the information for the table 'xxx' > > What is the reasen for the problem ? > > What can I do ? > > Best regards >
Axel, I've not seent his before. What service pack level are you using on pub/dist/subs (also is it SQL 2000)? Are you using anything 'special' eg dynamic filters etc. Please cna you give the steps required to reproduce. Rgds, Paul Ibison, SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
Hi, I use on the publisher and all subscribers SQL-Server 2000 with Service Pack 3. I don't use any specials like dynamic filters and so on. I use the german version of SQL-Server 2000. Therfore I get a german error messages with no error number. Normaly I can search the original english error messages in the knowlegebase by the error number. Therfore I must translate the error message from german to english. I do this for my best, but I'am sure it's not the original message. Have I any chance to get the orignal english message on a german SQL-Server instance ? Best regards Axel Lanser [quoted text, click to view] "Paul Ibison" wrote: > Axel, > I've not seent his before. What service pack level are you using on > pub/dist/subs (also is it SQL 2000)? Are you using anything 'special' eg > dynamic filters etc. Please cna you give the steps required to reproduce. > Rgds, > Paul Ibison, SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html) > >
Axel, please can you post up the error number for me. TIA, Paul Ibison [quoted text, click to view] "ALN" <ALN@discussions.microsoft.com> wrote in message news:B322ED30-962E-435A-9082-945FDCD5A6CD@microsoft.com... > Hi, > I use on the publisher and all subscribers SQL-Server 2000 with Service > Pack > 3. > > I don't use any specials like dynamic filters and so on. > > I use the german version of SQL-Server 2000. Therfore I get a german error > messages with no error number. Normaly I can search the original english > error messages in the knowlegebase by the error number. Therfore I must > translate the error message from german to english. I do this for my best, > but I'am sure it's not the original message. > > Have I any chance to get the orignal english message on a german > SQL-Server > instance ? > > Best regards > > Axel Lanser > > "Paul Ibison" wrote: > >> Axel, >> I've not seent his before. What service pack level are you using on >> pub/dist/subs (also is it SQL 2000)? Are you using anything 'special' eg >> dynamic filters etc. Please cna you give the steps required to reproduce. >> Rgds, >> Paul Ibison, SQL Server MVP, www.replicationanswers.com >> (recommended sql server 2000 replication book: >> http://www.nwsu.com/0974973602p.html) >> >> >>
Hi, that's my problem. The merge-agent errors have no error numbers. Best regards Axel Lanser [quoted text, click to view] "Paul Ibison" wrote: > Axel, > please can you post up the error number for me. > TIA, > Paul Ibison > > "ALN" <ALN@discussions.microsoft.com> wrote in message > news:B322ED30-962E-435A-9082-945FDCD5A6CD@microsoft.com... > > Hi, > > I use on the publisher and all subscribers SQL-Server 2000 with Service > > Pack > > 3. > > > > I don't use any specials like dynamic filters and so on. > > > > I use the german version of SQL-Server 2000. Therfore I get a german error > > messages with no error number. Normaly I can search the original english > > error messages in the knowlegebase by the error number. Therfore I must > > translate the error message from german to english. I do this for my best, > > but I'am sure it's not the original message. > > > > Have I any chance to get the orignal english message on a german > > SQL-Server > > instance ? > > > > Best regards > > > > Axel Lanser > > > > "Paul Ibison" wrote: > > > >> Axel, > >> I've not seent his before. What service pack level are you using on > >> pub/dist/subs (also is it SQL 2000)? Are you using anything 'special' eg > >> dynamic filters etc. Please cna you give the steps required to reproduce. > >> Rgds, > >> Paul Ibison, SQL Server MVP, www.replicationanswers.com > >> (recommended sql server 2000 replication book: > >> http://www.nwsu.com/0974973602p.html) > >> > >> > >> > >
Hi, the errornumber is -2147201016. Best reagrds Axel Lanser The Logfile follows: Microsoft SQL Server-Merge-Agent 8.00.760 Copyright (c) 2000 Microsoft Corporation Microsoft SQL Server-Replikations-Agent: 2003-SERVER\VERLEGER-TV_LAUSITZ-TV_LAUSITZ-2003-SERVER\ABONNENT-17 Percent Complete: 0 Verbindung mit Verteiler '2003-SERVER\VERLEGER' Connecting to Verteiler '2003-SERVER\VERLEGER.' Server: 2003-SERVER\VERLEGER DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:55]2003-SERVER\VERLEGER.: {call sp_MSgetversion } [29.03.2005 19:03:55]2003-SERVER\VERLEGER.: {call sp_helpdistpublisher (N'2003-SERVER\VERLEGER') } [29.03.2005 19:03:55]2003-SERVER\VERLEGER.distribution: select datasource, srvid from master..sysservers where upper(srvname) = upper(N'2003-SERVER\VERLEGER') [29.03.2005 19:03:55]2003-SERVER\VERLEGER.distribution: select datasource, srvid from master..sysservers where upper(srvname) = upper(N'2003-SERVER\ABONNENT') [29.03.2005 19:03:55]2003-SERVER\VERLEGER.distribution: {call sp_MShelp_merge_agentid (0, N'TV_LAUSITZ', N'TV_LAUSITZ', 5, N'TV_LAUSITZ')} [29.03.2005 19:03:55]2003-SERVER\VERLEGER.distribution: {call sp_MShelp_profile (17, 4, N'')} Percent Complete: 0 Initialisiert Connecting to Verleger '2003-SERVER\VERLEGER.TV_LAUSITZ' Percent Complete: 1 Verbindung mit Verleger '2003-SERVER\VERLEGER' Server: 2003-SERVER\VERLEGER DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:56]2003-SERVER\VERLEGER.TV_LAUSITZ: set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle' Connecting to Verleger '2003-SERVER\VERLEGER.TV_LAUSITZ' Server: 2003-SERVER\VERLEGER DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:56]2003-SERVER\VERLEGER.TV_LAUSITZ: {call sp_MSgetversion } [29.03.2005 19:03:56]2003-SERVER\VERLEGER.distribution: {call sp_MShelp_subscriber_info (N'2003-SERVER\VERLEGER', N'2003-SERVER\ABONNENT')} Connecting to Abonnent '2003-SERVER\ABONNENT.TV_LAUSITZ' Server: 2003-SERVER\ABONNENT DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:56]2003-SERVER\ABONNENT.TV_LAUSITZ: {call sp_MSgetversion } Percent Complete: 2 Verbindung mit Abonnent '2003-SERVER\ABONNENT' Percent Complete: 3 Ruft Publikationsinformationen ab Percent Complete: 4 Ruft Abonnementinformationen ab Percent Complete: 4 Der Mergeprozess führt einen Cleanup für die Metadaten in der TV_LAUSITZ-Datenbank aus. Percent Complete: 4 Der Mergeprozess hat einen Cleanup für 0 Zeile(n) in "MSmerge_genhistory", 0 Zeile(n) in "MSmerge_contents" und 0 Zeile(n) in "MSmerge_tombstone" ausgeführt. Percent Complete: 4 Der Mergeprozess führt einen Cleanup für die Metadaten in der TV_LAUSITZ-Datenbank aus. Percent Complete: 4 Der Mergeprozess hat einen Cleanup für 0 Zeile(n) in "MSmerge_genhistory", 0 Zeile(n) in "MSmerge_contents" und 0 Zeile(n) in "MSmerge_tombstone" ausgeführt. Percent Complete: 4 Uploadet Datenänderungen zum Verleger Connecting to Abonnent '2003-SERVER\ABONNENT.TV_LAUSITZ' Server: 2003-SERVER\ABONNENT DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:57]2003-SERVER\ABONNENT.TV_LAUSITZ: {call sp_MSgetversion } Connecting to Verleger '2003-SERVER\VERLEGER.TV_LAUSITZ' Server: 2003-SERVER\VERLEGER DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:57]2003-SERVER\VERLEGER.TV_LAUSITZ: {call sp_MSgetversion } Connecting to Abonnent '2003-SERVER\ABONNENT.TV_LAUSITZ' Server: 2003-SERVER\ABONNENT DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [29.03.2005 19:03:57]2003-SERVER\ABONNENT.TV_LAUSITZ: {call sp_MSgetversion } Connecting to Verleger '2003-SERVER\VERLEGER.TV_LAUSITZ' Server: 2003-SERVER\VERLEGER DBMS: Microsoft SQL Server Version: 08.00.0760 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024
Hi, I use SQL-server 2000 with service pack 3. I don't use any filters. The two articles don't help me. I generate a SQL-script from the tables which produce the problem to show you the schema definitions. Now follows the SQL-Script: CREATE TABLE [dbo].[LISA_ZNFLURSTK] ( [LBER] [int] NULL , [LAND1] [nvarchar] (3) COLLATE Latin1_General_CS_AS NULL , [BLAND] [int] NULL , [BEZEI] [nvarchar] (20) COLLATE Latin1_General_CS_AS NULL , [KREIS_ID] [int] NULL , [KREIS_NAME] [nvarchar] (35) COLLATE Latin1_General_CS_AS NULL , [GMDNR] [int] NULL , [GEMEINDE_NAME] [nvarchar] (35) COLLATE Latin1_General_CS_AS NULL , [GEMARKUNG_NAME] [nvarchar] (35) COLLATE Latin1_General_CS_AS NULL , [KBZLISA] [nvarchar] (5) COLLATE Latin1_General_CS_AS NOT NULL , [GRLFD] [int] NOT NULL , [FLURK] [int] NOT NULL , [FLURZB] [nvarchar] (10) COLLATE Latin1_General_CS_AS NULL , [FLURN] [int] NOT NULL , [KBZLIS] [nvarchar] (20) COLLATE Latin1_General_CS_AS NULL , [BEARB_ID] [nvarchar] (12) COLLATE Latin1_General_CS_AS NULL , [GR_KAT] [int] NULL , [FREIST] [nvarchar] (1) COLLATE Latin1_General_CS_AS NULL , [ART_FRST] [nvarchar] (7) COLLATE Latin1_General_CS_AS NULL , [STAT] [nvarchar] (1) COLLATE Latin1_General_CS_AS NULL , [AMT_ID] [nvarchar] (3) COLLATE Latin1_General_CS_AS NULL , [GBBEZ] [nvarchar] (5) COLLATE Latin1_General_CS_AS NULL , [GBBAND] [nvarchar] (5) COLLATE Latin1_General_CS_AS NULL , [GBBLATT] [int] NULL , [BEMERK_1] [nvarchar] (80) COLLATE Latin1_General_CS_AS NULL , [BEMERK_2] [nvarchar] (80) COLLATE Latin1_General_CS_AS NULL , [BEMERK_3] [nvarchar] (80) COLLATE Latin1_General_CS_AS NULL , [HINWEIS_1] [nvarchar] (80) COLLATE Latin1_General_CS_AS NULL , [HINWEIS_2] [nvarchar] (80) COLLATE Latin1_General_CS_AS NULL , [HINWEIS_3] [nvarchar] (80) COLLATE Latin1_General_CS_AS NULL , [ENTST_ID] [nvarchar] (10) COLLATE Latin1_General_CS_AS NULL , [WURDE_ZU] [nvarchar] (10) COLLATE Latin1_General_CS_AS NULL , [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL ) ON [PRIMARY] GO CREATE TABLE [dbo].[TGS_DGNS_LISA_ZNFLURSTK] ( [ID] [int] IDENTITY (1, 1) NOT NULL , [DATEI] [nvarchar] (255) COLLATE Latin1_General_CS_AS NOT NULL , [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL ) ON [PRIMARY] GO CREATE TABLE [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK] ( [ID] [int] NOT NULL , [MSLINK] [int] NOT NULL , [KBZLISA] [nvarchar] (10) COLLATE Latin1_General_CS_AS NOT NULL , [GRLFD] [float] NOT NULL , [FLURK] [float] NOT NULL , [FLURN] [float] NOT NULL , [MINX] [float] NOT NULL , [MINY] [float] NOT NULL , [MAXX] [float] NOT NULL , [MAXY] [float] NOT NULL , [DATEIID] [int] NOT NULL , [DOCHCHECK] [bit] NULL , [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL ) ON [PRIMARY] GO CREATE TABLE [dbo].[TGS_UMRINGPKTE_LISA_ZNFLURSTK] ( [ID] [int] NOT NULL , [PKTNR] [int] NOT NULL , [RW] [float] NOT NULL , [HW] [float] NOT NULL , [DATEIID] [int] NOT NULL , [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL ) ON [PRIMARY] GO ALTER TABLE [dbo].[TGS_DGNS_LISA_ZNFLURSTK] WITH NOCHECK ADD CONSTRAINT [PK_TGS_DGNS_LISA_ZNFLURSTK] PRIMARY KEY CLUSTERED ( [ID] ) ON [PRIMARY] GO ALTER TABLE [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK] WITH NOCHECK ADD CONSTRAINT [PK_TGS_UMRINGE_LISA_ZNFLURSTK] PRIMARY KEY CLUSTERED ( [ID] ) ON [PRIMARY] GO ALTER TABLE [dbo].[LISA_ZNFLURSTK] WITH NOCHECK ADD CONSTRAINT [DF__LISA_ZNFL__rowgu__0EF901FB] DEFAULT (newid()) FOR [rowguid] GO ALTER TABLE [dbo].[TGS_DGNS_LISA_ZNFLURSTK] WITH NOCHECK ADD CONSTRAINT [DF__TGS_DGNS___rowgu__008AE713] DEFAULT (newid()) FOR [rowguid] GO ALTER TABLE [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK] WITH NOCHECK ADD CONSTRAINT [DF__TGS_UMRIN__rowgu__43F7A576] DEFAULT (newid()) FOR [rowguid] GO ALTER TABLE [dbo].[TGS_UMRINGPKTE_LISA_ZNFLURSTK] WITH NOCHECK ADD CONSTRAINT [DF__TGS_UMRIN__rowgu__78AB64D7] DEFAULT (newid()) FOR [rowguid] GO CREATE UNIQUE INDEX [index_617769258] ON [dbo].[LISA_ZNFLURSTK]([rowguid]) ON [PRIMARY] GO CREATE UNIQUE INDEX [index_1630628852] ON [dbo].[TGS_DGNS_LISA_ZNFLURSTK]([rowguid]) ON [PRIMARY] GO CREATE INDEX [KBZLISA_IDX] ON [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK]([KBZLISA]) ON [PRIMARY] GO CREATE INDEX [GRLFD_IDX] ON [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK]([GRLFD]) ON [PRIMARY] GO CREATE INDEX [FLURK_IDX] ON [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK]([FLURK]) ON [PRIMARY] GO CREATE INDEX [FLURN_IDX] ON [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK]([FLURN]) ON [PRIMARY] GO CREATE UNIQUE INDEX [index_777769828] ON [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK]([rowguid]) ON [PRIMARY] GO CREATE INDEX [ID_IDX] ON [dbo].[TGS_UMRINGPKTE_LISA_ZNFLURSTK]([ID]) ON [PRIMARY] GO CREATE INDEX [PKTNR_IDX] ON [dbo].[TGS_UMRINGPKTE_LISA_ZNFLURSTK]([PKTNR]) ON [PRIMARY] GO CREATE UNIQUE INDEX [index_569769087] ON [dbo].[TGS_UMRINGPKTE_LISA_ZNFLURSTK]([rowguid]) ON [PRIMARY] GO ALTER TABLE [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK] ADD CONSTRAINT [FK_TGS_UMRINGE_LISA_ZNFLURSTK_TGS_DGNS_LISA_ZNFLURSTK] FOREIGN KEY ( [DATEIID] ) REFERENCES [dbo].[TGS_DGNS_LISA_ZNFLURSTK] ( [ID] ) ON DELETE CASCADE ON UPDATE CASCADE GO ALTER TABLE [dbo].[TGS_UMRINGPKTE_LISA_ZNFLURSTK] ADD CONSTRAINT [FK_TGS_UMRINGPKTE_LISA_ZNFLURSTK_TGS_UMRINGE_LISA_ZNFLURSTK] FOREIGN KEY ( [ID] ) REFERENCES [dbo].[TGS_UMRINGE_LISA_ZNFLURSTK] ( [ID] ) ON DELETE CASCADE ON UPDATE CASCADE GO
OK - I also use sp3 and have created the same publication as yourself without any issues. If restarting the merge agent doesn't fix this issue, then check the installation logs of sp3 on both boxes to ensure the install completed successfully and if so I'd open a support case. HTH, Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
Hi, thank you very much. I think I have solved my problem. The error seems to be a bug of the SQL-SERVER 8.00.760 (SP3). This morning I installed the following fix: Hot Fix for Microsoft Knowledge Base article number(s) 884850 Now I have SQL-SERVER 8.00.977 (SP3) and the merge-aggent works fine!!!! Best regards Axel Lanser [quoted text, click to view] "Paul Ibison" wrote: > OK - I also use sp3 and have created the same publication > as yourself without any issues. If restarting the merge > agent doesn't fix this issue, then check the installation > logs of sp3 on both boxes to ensure the install completed > successfully and if so I'd open a support case. > HTH, > Paul Ibison SQL Server MVP, > www.replicationanswers.com/default.asp > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html) >
Axel, thanks for the update. I considered this hotfix but the relevant error message was supposed to be "Message: Line 1: Incorrect syntax near '-'." Anyway, glad you're up and going again. Rgds, Paul [quoted text, click to view] "ALN" <ALN@discussions.microsoft.com> wrote in message news:74774B1D-F863-49E3-A9BB-6D3A353CC5F3@microsoft.com... > Hi, > thank you very much. > > I think I have solved my problem. > > The error seems to be a bug of the SQL-SERVER 8.00.760 (SP3). > > This morning I installed the following fix: > > Hot Fix for Microsoft Knowledge Base article number(s) 884850 > > Now I have SQL-SERVER 8.00.977 (SP3) and the merge-aggent works fine!!!! > > Best regards > > Axel Lanser > > "Paul Ibison" wrote: > >> OK - I also use sp3 and have created the same publication >> as yourself without any issues. If restarting the merge >> agent doesn't fix this issue, then check the installation >> logs of sp3 on both boxes to ensure the install completed >> successfully and if so I'd open a support case. >> HTH, >> Paul Ibison SQL Server MVP, >> www.replicationanswers.com/default.asp >> (recommended sql server 2000 replication book: >> http://www.nwsu.com/0974973602p.html) >> >>
Don't see what you're looking for? Try a search.
|
|
|