could not bulk copy out of table 'contE6E5BDF7F1C24EC588142A934ACF00D1'

Hi all,
Sorry to post this one again but I have added some more info....
I have a sql2000 SP3 merge replication set up using dynamic filters
to 29 sites/publications so each site only see's it's own data.
I have been adding new tables to the schema using sp_mergearticle
(but that is another story !!). I have been running the
sp_mergearticle , running the snapshot, merging, new tables published
...etc OK. I did this 10 times and then hit the error The process
could not bulk copy out of table
'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
agent for one of the publications.
I added the -output (Outputverboselevel 2) and got the follow info at
the end (it failes when it starts to bulk copy)
Bulk copying snapshot data for system table 'MSmerge_contents'
select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
[9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
SourceTypeId = 5
SourceName = GODZILLA
ErrorCode = 8624
ErrorText = Internal SQL Server error.
The process could not bulk copy out of table
'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
Disconnecting from Publisher 'GODZILLA'
I ran the profiler whilst the snapshot was generated, I could see the
view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
(any anything else it had temp created) Is there any way I can capture
the view before it is dropped or stop the drop from occuring. I am sure
if I can get hold of this view then I will be able to find the fault.
I am confused as to why this has been fine on 10 of the publications
then suddenly decided to error.
The file versions I have are:
SQLSRV32.DLL = 2000.81.9042.0
SQLSRV32.RLL = 2000.81.9001.0
odbcbcp.dll = 2000.81.9042.0
Thanks
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I've had my share of problems with dynamic filters, but not the one you are
encountering. Can you drop this subscription and filter and then try to
recreate it using another folder?
If you want to catch this transitory view you are best to query it in the
publication database.
IE repeatedly run
sp_helptext contE6E5BDF7F1C24EC588142A934ACF00D1
Or run profiler to try to capture its creation
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eesd36JnEHA.556@.tk2msftngp13.phx.gbl...
> Hi all,
> Sorry to post this one again but I have added some more info....
>
> I have a sql2000 SP3 merge replication set up using dynamic filters
> to 29 sites/publications so each site only see's it's own data.
> I have been adding new tables to the schema using sp_mergearticle
> (but that is another story !!). I have been running the
> sp_mergearticle , running the snapshot, merging, new tables published
> ...etc OK. I did this 10 times and then hit the error The process
> could not bulk copy out of table
> 'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
> agent for one of the publications.
> I added the -output (Outputverboselevel 2) and got the follow info at
> the end (it failes when it starts to bulk copy)
> Bulk copying snapshot data for system table 'MSmerge_contents'
> select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> [9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
> cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> SourceTypeId = 5
> SourceName = GODZILLA
> ErrorCode = 8624
> ErrorText = Internal SQL Server error.
> The process could not bulk copy out of table
> 'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
> Disconnecting from Publisher 'GODZILLA'
>
> I ran the profiler whilst the snapshot was generated, I could see the
> view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
> errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
> (any anything else it had temp created) Is there any way I can capture
> the view before it is dropped or stop the drop from occuring. I am sure
> if I can get hold of this view then I will be able to find the fault.
>
> I am confused as to why this has been fine on 10 of the publications
> then suddenly decided to error.
> The file versions I have are:
> SQLSRV32.DLL = 2000.81.9042.0
> SQLSRV32.RLL = 2000.81.9001.0
> odbcbcp.dll = 2000.81.9042.0
>
> Thanks
> Ian
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hilary,
Thanks for your responses.
The trouble is the temp view gets a new name each time I run the
snapshot so I do not know what to look for with sp_helptext.
I could drop the publication/subscription but it has over 100 tables
with un-merged data so I will have to manually put the data in(unless
there is an easier way that I do not know about ?)
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The way I view it you have about 4 options
1) call PSS
2) figure out the proc which is used to generate this view and modify it to
write a perm view.
3) create a new publication which has this problem filter in and deploy it
to the subscriber
4) backup the publication database and restore it on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eq1LVMMnEHA.608@.TK2MSFTNGP09.phx.gbl...
> Hilary,
> Thanks for your responses.
> The trouble is the temp view gets a new name each time I run the
> snapshot so I do not know what to look for with sp_helptext.
> I could drop the publication/subscription but it has over 100 tables
> with un-merged data so I will have to manually put the data in(unless
> there is an easier way that I do not know about ?)
> Regards,
> Ian
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||I've decided to raise a call at Microsoft. If I still cannot resolve
then I will just re-create the publication etc so I will loose nothing
by doing so (except a few ).
I will let you know the outcome.Thanks again for your responses.
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!