Restarting After Client or Teradata ARC Failure - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

If the client system or Teradata ARC fails during an archive, restore, or recovery procedure, restart the operation. Teradata ARC responds to the failure by logging all its sessions off the Teradata Database. The Teradata Database does not journal Teradata ARC statements, therefore Teradata ARC takes no recovery action at logoff. Database locks placed by a utility statement on databases or tables remain intact following a failure.

To restart a utility operation automatically, specify the RESTART runtime option when starting Teradata ARC. The restart log is used to determine the state of the pending operation. Command execution continues using the copy of the original source statement file. Teradata ARC reads the restart log to determine its restart point, then reenters the statement that was being processed at the time of the failure.

If a client or utility failure interrupted an archive or restore of database DBC, do not restart the operation.

If an archive or restore of multiple databases including database DBC is interrupted, resubmit the ARCHIVE statement. Or, specify the RESTART option.