December 15, 2013 at 5:41 pm
I have to replicate 14 tables and out of 14 only one table is refusing to replicate. Its transaction replication on sql server 2008 R2 (SP1) on win 2003 srv 64 bit.
I get the following error and if i run the bcp on cmd prompt it loads the data . I see people reporting similar issues for 2005 and suggestions but none are applicable to SQL SRV 2008.
"
Error messages:
The process could not bulk copy into table '"dbo"."TSR_ACCOUNT_VEHICLE"'. (Source: MSSQL_REPL, Error number:MSSQL_REPL20037)
Get help: http://help/MSSQL_REPL20037
Data conversion failed
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 "TPDB"."dbo"."TSR_ACCOUNT_VEHICLE" in "\\dotstodb035\ReplData\unc\ORADIST_DISTRIBUTION_PROD_ACCT_VEH\20131215184403\TSR_ACCOUNT_VEHICLE_2.bcp" -e "errorfile" -t"<x$3>" -r"<,@g>" -m10000 -SDOTSTOINFDB101 -T -w (Source: MSSQLServer, Error number: 20253)
Get help: http://help/20253
"
Thanks
P.S : i have also posted this on msdn web site since iam badly in need of an answer quickly , hope its ok.
December 16, 2013 at 1:13 am
Check that the TSR_ACCOUNT_VEHICLE table schema is the same between databases.
If it is, drop the article from publisher, drop table on subscriber. Add article, snapshot, should work according to this: http://www.sqlservercentral.com/blogs/jeffrey_yao/2008/06/03/replication-error-quot-field-size-too-large-quot/
December 16, 2013 at 2:16 am
Andrew G (12/16/2013)
Check that the TSR_ACCOUNT_VEHICLE table schema is the same between databases.If it is, drop the article from publisher, drop table on subscriber. Add article, snapshot, should work according to this: http://www.sqlservercentral.com/blogs/jeffrey_yao/2008/06/03/replication-error-quot-field-size-too-large-quot/
Or you could just modify the table on the subscriber to match that of the publisher (minus any identity column setting usually).
It seems strange that the schema would be different if it was initialised from a snapshot.
December 16, 2013 at 7:47 am
The table is identicle , I am not using identity columns, and this table replicates perfectly on other subscribers which tells me that it must have something to do with the environment settings.
also if the table structure was different i would not be able to manually run the bcp command which succeeeds if I run it on the DOS prompt.
I also set the article properties to truncate the table and not drop it, no luck.
December 16, 2013 at 8:17 pm
when i run the bcp in DOS window it loads the data but gives the following error, i think this might be my issue. but how to interpret this error? it doesnt show what exactly is wrong
#@ Row 11165008, Column 7: Invalid character value for cast specification @#
356323702041766013MEXFL012013-11-30 14:00:000000-00-00 00:00:00
December 16, 2013 at 9:03 pm
To me, that looks like column 7 has an invalid value "0000-00-00 00:00:00". Is there blank data for that column in the source?
Since it's a datetime, is there some sort of bad conversion going on with the date format? Check the default language of the login being used on that server, is it US_English? Is that the same as the other servers.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply