Teradata ARC does not record most of the modifications it makes to a database in the transient journal. Instead, Teradata ARC uses a file called restart log to maintain the operation status of the job being run.
The restart log catalogs the effects of utility operations on a database or table. Teradata ARC writes restart entries in the log at the beginning and end of each significant step (and at intermediate points in a long running task). If a job is interrupted for some reason, Teradata ARC uses this log to restart the archive or restore an operation that was being performed.
When Teradata ARC is started, it first places markers into the restart log to keep track of the current input and logon statements. Then Teradata ...
