BUG:LogReader Can Fail to Insert Jobs if Sync Task is Running

Last reviewed: May 2, 1997
Article ID: Q139890

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 11993 (6.00)

SYMPTOMS

The 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.

CAUSE

You 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.

WORKAROUND

Schedule 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."

STATUS

Microsoft 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
Keywords : kbbug6.00 kbusage SSrvRep
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.