1

We have a DB that is doing a transactional replication to one other server. There are three tables it is replicating in the DB. Yesterday the subscriber ran out of disk space. This caused the replication to fail. I tried to start it back up but the subscription failed with the error message

Invalid object name 'MSreplication_subscriptions'.

Currently the subscription is sitting in a "running" status, but states

The initial snapshot for publication <XXXXXX> is not yet available.

Is my only solution to reinitialize the subscription? I'm trying to avoid that if at all possible since the DB is quite large and our pipe isn't that large.

Improve this question
6
  • is the subscription expired ? If yes, then you have to reinit it. – Kin Shah Dec 4 '18 at 20:34
  • @Kin its not "expired". This publication in the properties --> "General" page "Subsriptions never expire, but they can be deactivated until they are reinitialized." So I assume that it was "deactivated" automatically due to the crash/drive filling up? – Kevin Vasko Dec 4 '18 at 20:57
  • Can you check using this script - dba.stackexchange.com/a/38999/8783 select * from distribution..MSsubscriptions where status = 0 – Kin Shah Dec 4 '18 at 21:12
  • @Kin It is empty. No rows returned. – Kevin Vasko Dec 4 '18 at 21:34
  • Did you do something else with the subscription DB? The transactions should be kept in the transaction log from the publisher, should just be a matter of restart the distribution agent again, which seems not the case. – dbamex Dec 4 '18 at 22:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.