July 7, 2003 at 9:23 am
We've added and dropped columns to a particular merge publication before, but this time it failed with error -2147201001, sp_repladdcolumn "Could not be propagated to the Subscriber".
The error occurred at only two subscribers, one of which is a backup site with little user activity.
It appears possible the subscriber is attempting, and failing, to gain an exclusive lock on the table to make the schema change. Does that make sense?
The problem at the backup site was resolved by putting the db into restricted access, which I am supposing ultimately had the effect of allowing a schema lock.
Any ideas how we might go about resolving this on the other server without having to reinitialize the publication?
July 10, 2003 at 9:33 am
I use repladd a lot, never had this happen. No good ideas.
Andy
July 10, 2003 at 9:52 am
The problem was not reading the error details closely enough. The failure was not with the proc, per se.
There was an ODBC timeout error during application of sp_replAddColumn because of the large table size.
The solution was to alter the agent profile, with -QueryTimeout set to 3600.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply