July 1, 2002 at 7:07 am
Ouch! Big Time!
We were setting up replication between two SQL 2000 SP2 servers when one of them crashed.
Since then, we have the following problems.
The distributor does not believe it is in replication with anything. No publishers or subscribers show, in fact nothing to indicate that any for of replication every took place. The same with the subscriber.
The only giveaways are that some of the tables have the field 'msrepl_tran_version' and a number of views exist with the name 'syncobj_*'.
If you try and modify or drop these tables, SQL 2000 tell you that you can't because they are used in replication.
If we try and re-establish replication, it fails on these tables with the error '@c4 is not defined'.
Nothing we do will get rid of this phantom replication on these tables, and short of destroying the database and restoring an old copy, we appear to be stuffed!
Does anyone know how to rollback this kind of problem?
---------------------------------------
It is by caffeine alone I set my mind in motion.
It is by the Beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
July 10, 2002 at 2:00 am
hello Rayven,
i don't know if this topic is still up-to-date for you - but i will answer nevertheless.
We have experienced similar problems - with the difference that our server did not crash, but replication was interrupted somehow with the result that not finished replication actions were hanging 'somewhere' afterwards. This was not recorded by any job-event-log and therefore we weren't aware of this and deleted the replication which was only a test anyway.
Well - the transaction logfile was growing immensely afterwards and when we investigated this we found out that there were pending transactions of the replication.
We solved this by setting up a new (dummy)replication in the same db, did some transactions, replicated them and then explicitly did 'sp_repldone' to tell the server that all transactions for any replication that he might have are done.
Afterwards we removed the dummy replication, re-done the implementation of this server as publisher and distributor and:
everything was 'clean' again!
Maybe this might be of use for your problem as well - or maybe for anybody else experiencing similar problems.
greetings,
kerstin
July 10, 2002 at 2:34 am
Many thanks, this sounds just like what has happened here, but the transaction log doesn't seem to be growing. I'll give this a try and let you know how I get on. Thanks for getting back to me after all this time.
---------------------------------------
It is by caffeine alone I set my mind in motion.
It is by the Beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply