May 28, 2004 at 1:04 am
I am facing problems on replication.
Some of the tables are not replicating.
I am giving you some messages given by Replication (Distribution) Agent.
----------
Bulk coping data into table 'AR_OUTSTAND'
Table "AR_OUTSTAND":100000 row(S) copied. Total:300000
Bulk copying data into table 'AR_COLL_HD'
Table "AR_COLL_HD":100000 row(S) copied. Total:100000
Bulk copying data into table 'AR_CRN_PROD_HD'
The process could not bulk copy into table "'AR_COLL_ADJ'"
-------------
I didn't find any difference (problem) in 'AR_COLL_ADJ' from other tables. There are lot of tables like this.
Why "'AR_COLL_ADJ'" has taken "' instead of ' ?
I disable the constraints in the article - table defaults. The same thing happened again.
Did anyone experience this?
Please help me.
Regards.
Boban
May 28, 2004 at 7:03 am
Are you applying the snapshot?
If so, try to manually import the snapshot to that table.
Locate the bcp file of that table, and then bulk insert it with the native format.
June 1, 2004 at 5:45 am
Hi,
Thanks for the reply.
But I have a lot of tables like that. So it is not feasible to adopt this method. I had given only one example.
2nd, I located the bcp file of that table, But I don't know hoe to bulk insert with native format. When I tried I got the message like following,
-----------------------------
Server: Msg 4863, Level 16, State 1, Line 1
Bulk insert data conversion error (truncation) for row 1, column 1 (COMP_ID).
Server: Msg 4866, Level 17, State 66, Line 1
Bulk Insert fails. Column is too long in the data file for row 1, column 23. Make sure the field terminator and row terminator are specified correctly.
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'STREAM' reported an error. The provider did not give any information about the error.
The statement has been terminated.
-----------------
June 3, 2004 at 7:01 am
Well my advice was to find the error, not to manually apply the snapshot.
To bulk insert do
BULK INSERT TableName FROM 'PathToBcpFile' WITH (DATAFILETYPE = 'NATIVE', CODEPAGE = 'ACP')
The error that you are getting it is because there is a diference between the table that you exported (that now it is in the bcp file) and the table that you are trying to import to.
Verify that both tables (in the publisher and the subscriber) are the same. If you found any difference, then the publisher table is right, and you must change the subscriber table.
June 6, 2004 at 7:05 pm
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply