Teradata FastLoad accumulates operational information about specific events that occur during a Teradata FastLoad job. If the Teradata FastLoad job script includes a NOTIFY command with an EXIT option specification, Teradata FastLoad calls the named Notify Exit routine and passes to it when the specific events occur:
- An event code to identify the event
- Specific information about the event
The table below lists the event codes and describes the data that Teradata FastLoad passes to the Notify Exit routine for each event. For a description of the events associated with each level of notification (low, medium, and high), see NOTIFY.
- User exits (INMOD and Notify Exit) should not make calls to the Teradata Call Level Interface (CLIv2). It can cause the normal operation of the utility to behave with unexpected results, and prevent requests from completing normally.
- To support future enhancements, always ensure that Notify exit Routines ignore invalid or undefined event codes, and that they do not cause Teradata FastLoad to terminate abnormally.
- Starting with Teradata Tools and Utilities 14.10, Teradata FastLoad supports 8-byte row counters. To display 8-byte counters in Notify events, use the new event with 64 as described in the following table and use the keyword EXIT64 rather than EXIT in the NOTIFY command.
- Starting with Teradata Tools and Utilities 14.10, Teradata FastLoad supports the EON feature. To display large object names in Notify events, use the new event with EON as described in Table 18 and use the keyword EXITEON rather than EXIT in the NOTIFY command. The keyword EXITEON automatically supports the keyword EXIT64.
Event Code | Event | Event Description | Data Passed to the Notify Exit Routine |
---|---|---|---|
0 | Initialize | Successful processing of the NOTIFY command |
|
1 | File or INMOD open | Successful processing of the DEFINE command that specifies the file or INMOD routine name. |
|
2 | Phase 1 begin | The beginning of the insert phase, where the table name is specified by the INSERT statement. |
|
3 | Checkpoint | Checkpoint information has been written to the restart log table. |
|
4 | Phase 1 end | The CHECKPOINT LOADING END request has successfully completed after the end of the insert phase. |
|
5 | Phase 2 begin | The END LOADING command is about to be sent to the database. | No data accompanies the phase 2 begin event code |
6 | Phase 2 end | Processing of the END LOADING command completed successfully. |
|
7 | Error table 1 | Processing of the SEL COUNT(*) request completed successfully for the first error table. |
|
8 | Error table 2 | Processing of the SEL COUNT(*) request completed successfully for the second error table. |
|
9 | Database restart | Teradata FastLoad received a crash message from the database or from CLIv2. | No data accompanies the database restart event code |
10 | CLIv2 error | Teradata FastLoad received a CLIv2 error. |
|
11 | Database error | Teradata FastLoad received a database error that will produce an exit code of 12. Not all database errors cause this event. An Error 3807, for example, while trying to drop or create a table does not terminate Teradata FastLoad.
|
|
12 | Exit | FastLoad is terminating. |
|
13 | Check point 64 | Checkpoint information has been written to the restart log table. |
|
14 | Phase I end 64 | The CHECKPOINT LOADING END request has successfully completed after the end of the insert phase. |
|
15 | Phase 2 end 64 | Processing of the END LOADING command completed successfully. |
|
16 | Error Table 1 64 | Processing of the SEL COUNT(*) request completed successfully for the first error table. |
|
17 | Error Table 2 64 | Processing of the SEL COUNT(*) request completed successfully for the second error table. |
|
18 | Initialize EON | Successful processing of the NOTIFY command |
|
19 | Phase 1 begin EON | The beginning of the insert phase, where the table name is specified by the INSERT statement. |
|