Teradata Parallel Data Pump

Chapter 5: Using INMOD and Notify Exit Routines
Overview
Table 37: Events Passed to the Notify Exit Routine (continued)
Event
Event
Code Event Description Data Passed to the Notify Exit Routine
Import begin 3 The first record is about to be read for
each import task
Import end 4 The last record has been read for each
import task. The returned data is the
record statistics for the import task
Error table 5 Processing of the SEL COUNT(*)
request completed successfully for the
error table
Import number—4-byte unsigned integer
• Import number—4-byte unsigned integer
• Records read—4-byte unsigned integer
• Records skipped—4-byte unsigned integer
• Records rejected—4-byte unsigned integer
• Records sent to Teradata Database—4-byte
unsigned integer
• Data errors—4-byte unsigned integer
• Table name—128-byte character (maximum) array
• Number of rows—4-byte unsigned integer
Teradata Database
restart
6 Teradata TPump received a crash
message from Teradata Database or
from the CLIv2
No data accompanies the Teradata Database restart
event code
CLIv2 error 7 Teradata TPump received a CLIv2
error
Error code—4-byte unsigned integer
Teradata Database
error
8 Teradata TPump received a Teradata
Database error that will produce an
exit code of 12
Error code—4-byte unsigned integer
Note: Not all Teradata Database errors cause this
event. A 3807 error, for example, while trying to drop
or create a table, does not terminate Teradata TPump.
Exit 9 Teradata TPump completed a load
task
Table statistics 10 Teradata TPump has successfully
written the table statistics
Checkpoint end 11 Teradata TPump successfully
completed the checkpoint operation
Exit code—4-byte unsigned integer
• Type (I = Insert, U = Update, or D = Delete) —
1-byte character variable
• Database name—64-character (maximum) array
• Table/macro name—64-character (maximum)
array
• Activity count—4-byte unsigned integer
Record number—4-byte unsigned integer
Teradata Parallel Data Pump Reference 209