Teradata Parallel Data Pump

Chapter 3: Teradata TPump Commands
BEGIN LOAD
Table 26: Events that Create Notifications (continued)
Notification Level
Checkpoint End No No Yes Yes Teradata TPump successfully
completed a checkpoint.
CLIv2 Error Yes Yes Yes Yes Teradata TPump received a CLIv2
error.
Database Error Yes Yes Yes Yes A Teradata Database error that
terminates Teradata TPump.
DML Error No No Yes Yes Teradata TPump is about to log a
DML error to the error table.
Error Table No No Yes Yes Successful processing of the SEL
COUNT(*) request for the error
table.
Exit Yes Yes Yes Yes Teradata TPump completed a load
task.
File or INMOD Open No No Yes Yes Successful processing of the
IMPORT command.
Import Begin No No Yes Yes Teradata TPump is about to start
reading records.
Import End No No Yes Yes Last record has been read.
Initialize Yes Yes Yes Yes Successful processing of the Notify
option (BEGIN LOAD command)
Interim Run Statistics No No No Yes Teradata TPump is about to update
the Monitor Interface table, or
Teradata TPump successfully
completed a checkpoint, or an
Import has just completed
successfully.
Table Statistics No Yes Yes Yes Teradata TPump has successfully
written the table statistics.
Teradata Database
Restart
No Yes Yes Yes Teradata TPump received a crash
error from Teradata or CLI.
Usage Notes
Multiple tables can be targeted by a single Teradata TPump job.
If the script author is uncertain whether or not to use ROBUST restart logic, it is always safe to
use the ROBUST ON parameter.
To ensure data integrity, the SERIALIZE parameter defaults to ON in the absence of an
explicit value if there are upserts in the Teradata TPump job.
The statement rate per minute you set using the RATE keyword is also affected by the
periodicity value. By default, Teradata TPump uses a periodicity value of four when enforcing
106 Teradata Parallel Data Pump Reference