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
Interim run
statistics
12 Teradata TPump is updating the
Monitor Interface table, has just
completed a checkpoint, or has read
the last record for an import task. The
returned data is the statistics for the
current load
• Import number—4-byte unsigned integer
• Statements sent to Teradata Database—4-byte
unsigned integer
• Requests sent to Teradata Database—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
DML error 13 Teradata TPump received a Teradata
Database error that was caused by
DML and will introduce an error-row
insert to the error table
• Import number—4-byte unsigned integer
• Error code—4-byte unsigned integer
• Error message—256-character (maximum) array
• Record number—4-byte unsigned integer
• Apply number—1-byte unsigned char
• DML number—1-byte unsigned char
• Statement number—1-byte unsigned char
• Record data—64,004-character (maximum) array
• Record data length—4-byte unsigned integer
• Feedback—a pointer to 4-byte unsigned integer
“Feedback” always points to integer 0 when it is passed
to the user exit routine. The user may change the value
of this integer to 1 to instruct Teradata TPump not to
log the error to the error table. In this case, Teradata
TPump will not log the error, but continue other
regular process on this error.
210 Teradata Parallel Data Pump Reference