• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 19 subscribers
  • Views 7581 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Capture Stopped as Archive Log missing due to deletion

mijanur.rahman
over 6 years ago

Capture Log stopped as the archive log deleted before it captured.

Now, how to re-sync the processes without the archive log.

 

BR/Mijan

Parents
  • 0 over 6 years ago

    I can't think of a "quick fix" - you're going to need to at the least clean out the queues and restart replication. Depending on how many tables are "out of sync" and how large they are, you'll need to correct them using compare (which will tell you which tables are out of sync and how badly) and repair, copy or a complete export/import. If there are large tables or lots of tables out of sync, you might be better off just "starting from scratch". I'd definitely recommend opening a Support Case - they might have other options and can suggest the most efficient ways to clear out the queues.

Reply
  • 0 over 6 years ago

    I can't think of a "quick fix" - you're going to need to at the least clean out the queues and restart replication. Depending on how many tables are "out of sync" and how large they are, you'll need to correct them using compare (which will tell you which tables are out of sync and how badly) and repair, copy or a complete export/import. If there are large tables or lots of tables out of sync, you might be better off just "starting from scratch". I'd definitely recommend opening a Support Case - they might have other options and can suggest the most efficient ways to clear out the queues.

Children
No Data