CHECKPOINT - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

CHECKPOINT

Purpose  

The CHECKPOINT parameter saves restart information in the restart log at the intervals specified by this parameter.

Syntax  

where

 

Syntax Element

Definition

n

Number of data blocks processed before the checkpoint is taken.

The maximum number of blocks is 10000000. Suffix K replaces three zeros (000). Setting CHECKPOINT to 0 disables ARC’s GetPos request.

If CHECKPOINT is not specified, the default number of blocks is 10000 for IBM and 32000 for Windows.

Usage Notes  

Both archive and restore/copy operations take checkpoints in the data phase. Every time the specified number of data blocks are processed, Teradata ARC saves the tape positioning and other processing information in the restart log. The frequency of checkpoint operations is controlled by the number of data blocks processed.

Checkpoint operations causes I/Os and additional processing overhead, therefore too many checkpoints might adversely impact performance. Each Teradata ARC data block contains up to 32K.

The CHECKPOINT parameter also controls the frequency of VERBOSE display, if active. To see the amount of data processed every minute with an approximate archive rate of 1MB/second, set the CHECKPOINT value between 2500 and 4500.

  • Setting a checkpoint frequency too high (a low CHECKPOINT value) might impact performance.
  • Setting a checkpoint frequency too low (a high CHECKPOINT value) causes Teradata ARC to reprocess a large number of data blocks in case of a restart.
  • Note: The CHECKPOINT runtime parameter only applies to Mainframe systems (z/OS) and network-attached systems.