Replication with errors

  • Hi All,

    I run into problems:

    Error messages:

    ·          The process could not bulk copy into table '"t_ElecConnData"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)

    Get help: http://help/MSSQL_REPL20037

    ·          Field size too large

    ·          To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below.  Consult the BOL for more information on the bcp utility and its supported options. (Source: MSSQLServer, Error number: 20253)

    Get help: http://help/20253

    bcp "JAW_TEST_TWO".."t_ElecConnData" in "C:\SWEETWATER_ReplData\unc\GHS0016RPT_SITEDATA_GARRADHASSAN_SITEDATA_4c7573d6\20070129071646\t_ElecConnData_7.bcp" -e "errorfile" -t"\n<x$3>\n" -r"\n<,@g>\n" -m10000 -S14419-26632 -T -w (Source: MSSQLServer, Error number: 20253)

    Get help: http://help/20253

    Can anyone helps pls?

    Thanks

    TJ

  • Is source and destination table has the same schema?

     

    MohammedU
    Microsoft SQL Server MVP

  • how to check the db schema?

    Sorry, I am newbee DBA

     

  • how did you originally create the publication? have you tried to reinitialize it?

  • Script the objects using SSMS and compare them manually if you don't have any coparison tool..

    Did you initialize the snapshot?

    MohammedU
    Microsoft SQL Server MVP

  • Did you try what the error message says to do?  Execute the BCP command manually to get the error results in a file called "errorfile". 

    I'd try that and see if you get any more detailed information.

  • The initial snapshoot went complete with no errors.

  • If initial snapshot completed then how BCP is being executed?

     

    MohammedU
    Microsoft SQL Server MVP

  • I think the error happens when the distribution agent applies the snapshot at the subscriber.

  • Hi Addict,

    That's correct.  I am getting the errors when the distribution agent applies the snapshoot at the subscriber.

    Thanks

    TJ

  • first stop the distribution

    then remove the subscription

    truncate the destination table

    run the BCP to transfer the data from source to destination.

    add the subscription again using @sync_type parameter set to "replication support only"

    Run the distribution.

  • It's because your source table's data type/format are out of the range of destination tables.

    Usually it's "Date" type.

    @Peandaddy

  • I am sure this problem begins with datatype , any constraints missing between Pub. DB to sub. DB tables , please recreate the table from Pub DB and ran it on Sub db..

    or find out the differences between the tables and do it manually.. surely the problem will be solved 🙂

Viewing 13 posts - 1 through 12 (of 12 total)

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