15.10 - Checkpoint Processing - Access Module

Teradata Tools and Utilities Access Module Reference

Access Module
Programming Reference

Checkpoint Processing

If checkpointing is enabled, the access module reads messages from the queue, then copies the data into a fallback file before delivering the data to the Data Connector. If the load utility decides to restart at an earlier point in the data stream, it directs the Data Connector to issue the File Set Position command to the access module. The module then supplies data from the fallback data file until the restart is complete.

After a position request is made to the access module, additional processing by the client (and probably the database) occurs. A checkpoint request is considered successful only after a subsequent request from the client is received by the access module. A checkpoint followed by a function request for a reposition is considered successful by virtue of the contents of the position information provided at the reposition. Support for a previous checkpoint is not removed until the most recent checkpoint is successful. This approach allows recovery from a checkpoint failure.

When a reposition request immediately follows an open request, a restart is conducted. In this case, one or more messages are retrieved from the checkpoint file before the messages are sent back to the access module.

Only the load feature of the Teradata Access Module for JMS supports checkpoint and restart capability for data recovery. Checkpoint and restarts are not supported during exports.