Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
jisakson
Starting Member
7 Posts |
Posted - 2008-08-15 : 16:43:30
|
I'm setting up transactional replication with subscriber updates.Publisher memory 4GB Subscriber 3GB. Both W2K3 Standard SP2. Both SQL Server 2005 Standard SP2. Both have at least 70GB free hard drive space.Successfully created the snapshot on publisher. Setup pull subscription on subscriber. Subscriber is pulling the initial snapshot and about halfway through errors on TABLENAME_144.bcp. The file size is 4,011,481 KB. The following errors are displayed. Any ideas would be appreciated.Error messages:The process could not bulk copy into table '"dbo"."TABLENAME"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)Get help: http://help/MSSQL_REPL20037memory mapped file read failedTo 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/20253bcp "DB"."dbo"."TABLENAME" in "\\sql-server\SQLrepl\unc\PUB_DATA_UPDATABLE_7ebde4df\20080815112209\TABLENAME_144.bcp" -e "errorfile" -t"\n<x$3>\n" -r"\n<,@g>\n" -m10000 -STLCDATAREPL -T -w (Source: MSSQLServer, Error number: 20253)Thanks,Jamie |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-08-15 : 16:46:20
|
How big is that table? |
|
|
jisakson
Starting Member
7 Posts |
Posted - 2008-08-15 : 16:54:24
|
130 million rows, table occupies 6GB of 20GB database file, index occupies 3GB. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-08-16 : 01:25:11
|
http://blogs.sqlservercentral.com/jeffrey_yao/archive/2008/07/02/replication-error-quot-memory-mapped-file-read-failed-quot.aspx |
|
|
jisakson
Starting Member
7 Posts |
Posted - 2008-08-18 : 09:05:57
|
A new twist to this error. Friday evening the the snapshot ultimately finished loading to the subscriber successfully. I'm at a lose for what caused this to happen and why after a few failures on the same file it finished. I'm guessing some timing/timeout issue or network issue. Our staff had started to leave on Friday when replication was able to successfully get past the 4GB file.I'll be testing this some more and post my findings.Thanks sodeep for your replies. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-08-18 : 23:05:06
|
You can set network monitor to find out what happens on the network during snapshot. |
|
|
|
|
|