Change the Recovery Log Size | Teradata Unity - 17.00 - Changing the Recovery Log Size - Continuous Availability - Teradata Unity

Teradata® Unity™ User Guide

Product
Continuous Availability
Teradata Unity
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2020-09-15
dita:mapPath
fmz1594836948704.ditamap
dita:ditavalPath
qqk1595871525984.ditaval
When you change the recovery log size, you must delete the recovery log file. Changing the recovery log size removes the Unity object state information. After the sequencers are started, all systems exist in the unrecoverable state. To promote systems to an active state, see Activating a Managed System.
Important: All objects managed by Unity remain in an unsynced state after this process is completed.
  1. From unityadmin, change the RecoveryLogSize parameter value to the new size in gigabytes:
    CONFIG UPDATE SEQUENCER RecoveryLogSize <newSize> REASON 'Increasing recovery log size';
  2. Retrieve the recovery log file name and path.
    The default location is /data/recovery.log. The recovery log path is stored in the configuration variable, RecoveryLogPath, and the filename is stored in the configuration key RecoveryLogName.
    Run the unityadmin commands config list key RecoveryLogPath and config list key RecoveryLogName to query the current setting for these parameters.
  3. Run the following commands to resize the recovery log.
    Resizing the recovery log involves the deletion of the current recovery log file. Make sure all systems and objects are fully recovered and in the active state before running the following commands.
    1. Stop both sequencer processes:
      /etc/init.d/unity stop
    2. Remove the old recovery log file on both Unity servers:
      rm /data/recovery.log
    3. Restart the sequencer processes on both Unity servers:
      /etc/init.d/unity start
  4. Reactivate the cluster.