Restarting a restore operation causes Teradata ARC to:
- Reposition the input archive file at the data block indicated in the last restart point recorded in the restart log before the failure occurred.
- If the AMP configuration changed (AMPs are online before the failure but offline afterward), restart begins with the last table being restored before the failure.
- For the table you are restarting, rebuild the deferred build list from the build steps saved in the Restart Log.
If a restore of database DBC is interrupted for any reason, perform the entire restoration again, including reinitializing the Teradata Database. Even if the Teradata Database was initialized prior to database DBC restore, initialize it again.
Example: Restarting a Restore on z/OS
For z/OS, the only difference between the original job and the restarted job is to add the RESTART parameter to the PARM statement of the EXEC.
//DBCRST1 JOB 1,’DBC OPERATIONS’,REGION=2048K,MSGCLASS=A //RESTORE EXEC PGM=ARCMAIN,PARM=’RESTART’ //STEPLIB DD DSN=DBC.AUTHLOAD,DISP=SHR // DD DSN=DBC.TRLOAD,DISP=SHR //DBCLOG DD DSN=DBC.ARCLOG.DATA,DISP=OLD //DUMP100 DD DSN=DBC.DUMP100,DISP=OLD //SYSPRINT DD SYSOUT=*,DCB=(RECFM=F,BLKSIZE=132,LRECL=132) //SYSIN DD DATA,DLM=## LOGON DBC,DBC; RESTORE DATA TABLES (PERSONNEL) ALL, RELEASE LOCK, FILE=DUMP100; LOGOFF; ##