SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


(Source: MSSQLServer, Error number: 20598)


(Source: MSSQLServer, Error number: 20598)

Author
Message
johnebonin
johnebonin
SSC-Enthusiastic
SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)

Group: General Forum Members
Points: 100 Visits: 102
Hello i am having and issue with replication i am receiving the following

Command attempted:
if @@trancount > 0 rollback tran
(Transaction sequence number: 0x000004850000013C000600000000, Command ID: 1)

Error messages:
The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)
Get help: http://help/20598

I have tried applying 953752 Cumulative update package 9 for SQL Server 2005 Service Pack 2 to resolve this issue but so far to date this has not resolved the issue.

Any help would be great.

Thanks
john_jakob
john_jakob
Mr or Mrs. 500
Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)

Group: General Forum Members
Points: 543 Visits: 100
I ran into this problem several times with SQL 2000 replication -- 2005 might be similar.

First try deleting all rows in the table in question at the subscriber, and start the replication going again--see if that works.

If that doesn't work, you might have to reinitialize the publication from scratch. Not a pleasant thing from anyone's perspective.

- j
johnebonin
johnebonin
SSC-Enthusiastic
SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)

Group: General Forum Members
Points: 100 Visits: 102
Thanks That has seem to resolve the issue.
john_jakob
john_jakob
Mr or Mrs. 500
Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)Mr or Mrs. 500 (543 reputation)

Group: General Forum Members
Points: 543 Visits: 100
Cool. Glad it helped.
Abhilash Melethil
Abhilash Melethil
SSC-Enthusiastic
SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)

Group: General Forum Members
Points: 157 Visits: 207
Thanks a ton for the solution!
Kendal Van Dyke
Kendal Van Dyke
SSCertifiable
SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)

Group: General Forum Members
Points: 5634 Visits: 983
john_jakob (8/29/2008)
I ran into this problem several times with SQL 2000 replication -- 2005 might be similar.

First try deleting all rows in the table in question at the subscriber, and start the replication going again--see if that works.

If that doesn't work, you might have to reinitialize the publication from scratch. Not a pleasant thing from anyone's perspective.

- j


There's a much more precise way to solve this. If you don't care about data consistency at the subscriber then simply change the distribution agent profile to ignore data consistency errors, restart the agent, and move on.

If you want to know the command that's failing then start by looking at the error in Replication Monitor or by executing sp_helpsubscriptionerrors (in the distribution database on the distributor). Syntax, including required parameters, can be found here: http://technet.microsoft.com/en-us/library/ms173427.aspx... that'll get you the xact_seqno and command_id.

You also need the publisher database id which you can get by runing this query on the distributor (substitute values in quotes for your situation):
SELECT  DISTINCT
subscriptions.publisher_database_id
FROM sys.servers AS [publishers]
INNER JOIN distribution.dbo.MSpublications AS [publications] ON publishers.server_id = publications.publisher_id
INNER JOIN distribution.dbo.MSarticles AS [articles] ON publications.publication_id = articles.publication_id
INNER JOIN distribution.dbo.MSsubscriptions AS [subscriptions] ON articles.article_id = subscriptions.article_id
AND articles.publication_id = subscriptions.publication_id
AND articles.publisher_db = subscriptions.publisher_db
AND articles.publisher_id = subscriptions.publisher_id
INNER JOIN sys.servers AS [subscribers] ON subscriptions.subscriber_id = subscribers.server_id
WHERE publishers.name = 'MyPublisher'
AND publications.publication = 'MyPublication'
AND subscribers.name = 'MySubscriber'



Now plug the xact_seqno, xact_seqno, and publisher_database_id into this query (again substituting the values with the ones you've gotten from the queries above):
EXECUTE distribution.dbo.sp_browsereplcmds
@xact_seqno_start = '0x0000001900001926000800000000',
@xact_seqno_end = '0x0000001900001926000800000000',
@publisher_database_id = 29,
@command_id = 1



Once you know what command is failing you can figure out what you need to change at the subscriber for replication to get past the error.

Kendal Van Dyke
http://kendalvandyke.blogspot.com/
via.mala
via.mala
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 74
WOW! That's something I can use!
Thx Kendal!
Chris Mackin-166947
Chris Mackin-166947
SSC-Addicted
SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)

Group: General Forum Members
Points: 467 Visits: 195
This is gold, thank you!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search