16.10 - Overriding Recovery Log Sync - Teradata Unity

Teradata Unity User Guide

Product
Teradata Unity
Release Number
16.10
Published
January 2018
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
anz1496162519675.ditamap
dita:ditavalPath
ft:empty

If the newly Active Sequencer is not able to contact the previously Active Sequencer to determine if the Recovery Log is in sync, then it will not become active. This protects against possible data loss if some transactions had not been applied on both managed systems.

To override this check and force the new Sequencer to become Active, you can run a command to take over the Sequencer.
Never force a takeover to the Standby Sequencer unless you have confirmed that the other sequencer or the Unity server it is running on has been shut down. If you force a takeover without confirming the sequencer or server are down, you can create a split-brain failure.
  1. At the unityadmin prompt, use the following command: SEQUENCER TAKEOVER BY FORCE
  2. Follow steps to re-sync the Repository.