Post reply

MSSQLServer, Error number : 3604

  • August 25, 2008 at 9:55 am

    #211501

    Hello room,

    I run into errors on my transaction replication with local distributor. The publisher database somehow is inserting a duplicate key

    These errors happened after the initial snapshot, and replication are completed.

    Command attempted:

    {CALL sp_MSins_t_FaultData (19, 27, 2008-08-18 00:07:10.087, 5.3380001e+001, 1708, -1621123112, 7, -1621122770, 0, -1621122770, 2008-08-19 00:21:49.000, 2100-12-31 00:00:00.000, 2008-08-18 00:11:10.250, 4.0040002e+000, 0, -1621122600)}

    (Transaction sequence number: 0x00001BAA00006AB6000100000000, Command ID: 34)

    Error messages:

    Duplicate key was ignored. (Source: MSSQLServer, Error number: 3604)

    Get help: http://help/3604

    Can anyone help and advice how to resolve it?

    Thanks,

    Edwin

  • August 28, 2008 at 12:18 pm

    #864620

    If it is only a record or few, just delete the duplicate from the subscriber database(s) and then replication will resume. Continue this until all duplicates are handled.

    If your setup results in common duplicates (like ours), then I'd recommend replacing the generated insert procedure with one of your own that uses TRY....CATCH to first try the INSERT, then do an UPDATE if the INSERT fails with a duplicate key error.

    Have Fun!
    Ronzo

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply