Restarting an Archive Operation - TARA/ABU

Restarting an Archive Operation

Restarting an archive operation causes Teradata ARC to:

Reposition the output 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 were online before the failure but offline afterward), restart begins with the last table being archived before the failure.

If archive of database DBC is interrupted, resubmit the ARCHIVE statement without specifying the RESTART option.

Example

The following example shows the restart of an all-AMPs archive on z/OS.

Note: The RESTART parameter has been added to the EXEC.

Restarting an Archive on z/OS

//DBCDMP1  JOB 1,’DBC OPERATIONS’,REGION=2048K,MSGCLASS=A    //DUMP     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 DISP=OLD,DSN=DBC.DUMP100

//SYSPRINT DD SYSOUT=*,DCB=(RECFM=F,BLKSIZE=132,LRECL=132)

//SYSUDUMP DD SYSOUT=*

//SYSIN    DD DATA,DLM=##

LOGON DBC,DBC;

ARCHIVE DATA TABLES (DBC) ALL,

   RELEASE LOCK,

   INDEXES,

   FILE=DUMP100;

LOGOFF;

##

In this example, the tape with VOLSER=DGJA is mounted at the time that Teradata ARC abends.

Note: When archiving on tape for z/OS, specify the tape level information and all tape volume serial numbers, including the one mounted at the time of the abend.