BUG:LogReader Can Fail to Insert Jobs if Sync Task is RunningLast reviewed: May 2, 1997Article ID: Q139890 |
The information in this article applies to:
SYMPTOMSThe LogReader replication task can fail with Msg 2601:
Unable to insert duplicate key row in object 'MSjobs' with unique index 'ucMSjobs'when you execute sp_MSadd_job while the SYNC task is executing.
CAUSEYou will most likely see this problem if the LogReader is continually reading published table changes from the transaction log while the SYNC task is executed. There is no relation to what publication is being "sync'd" for this problem. This problem will only occur if the SYNC task has to add new jobs as part of a new subscription or scheduled table refresh event. This problem may be rarely encountered even when the LogReader and SYNC tasks are running concurrently.
WORKAROUNDSchedule the LogReader and SYNC tasks to run at different times. -or- Reduce the batch size for the LogReader task (-b parameter). More information on this parameter can be found in the SQL Server "Administrator's Companion" in Chapter 16, "Scheduling Tasks."
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: sql6 replication jobs batch
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |