Backing Up PPI Data in the TransactionHistory Table - Teradata Tools and Utilities

Teradata® Archive/Recovery Utility Reference

Product
Teradata Tools and Utilities
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-06-05
dita:mapPath
fac1527114221922.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
Product Category
Teradata Tools and Utilities
  1. Perform a full-table archive:
    ARCHIVE DATA TABLES
        (SYSDBA.TransactionHistory),
    RELEASE LOCK,
    FILE=ARCHIVE;
  2. Set up incremental archives:
    ARCHIVE DATA TABLES
        (SYSDBA.TransactionHistory)
          ( PARTITIONS WHERE
            (! TransactionDate BETWEEN CURRENT_DATE – 3 AND CURRENT_DATE
              !) ),
    RELEASE LOCK,
    FILE=ARCHIVE;
    In this example, ‘CURRENT_DATE – 3’ archives a partition even after it becomes non-active, in case the final archive of the partition fails or the value of CURRENT_DATE changes during the final backup.
  3. Set up differential backups:
    ARCHIVE DATA TABLES
        (SYSDBA.TransactionHistory)
          ( PARTITIONS WHERE
            (! TransactionDate BETWEEN DATE ‘2004-01-01’ AND DATE ‘2004-03-31’
               !) ),
    RELEASE LOCK,
    FILE=ARCHIVE;
  4. (Optional) Perform a separate partition backup if updating a partition that is not archived by the incremental backup step (step 2):
    ARCHIVE DATA TABLES
        (SYSDBA.TransactionHistory)
          ( PARTITIONS WHERE
            (! TransactionDate = DATE ‘2004-03-15’
              !) ),
    RELEASE LOCK,
    FILE=ARCHIVE;