Teradata MultiLoad accumulates operational information about specific events that occur during a Teradata MultiLoad job. If the BEGIN MLOAD command or the BEGIN DELETE MLOAD command includes a NOTIFY option with an EXIT specification, then, when the specific events occur, Teradata MultiLoad calls the named notify exit routine and passes to it:
- An event code to identify the event
- Specific information about the event
The following table lists the event codes and describes the data that Teradata MultiLoad 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 the description of the NOTIFY command option for BEGIN MLOAD and BEGIN DELETE MLOAD.
Event Code | Event | Event Description | Data Passed to the Notify Exit Routine |
---|---|---|---|
0 | Initialize | Successful processing of the NOTIFY option of the BEGIN MLOAD or BEGIN DELETE MLOAD command |
|
1 | File or INMOD open | Successful processing of the IMPORT command that specifies the file or INMOD routine name |
|
2 | Phase 1 begin | The beginning of the acquisition
phase It is called one time for each table specified in the BEGIN MLOAD or BEGIN DELETE MLOADcommands. |
|
3 | Checkpoint | Checkpoint information has been written to the restart log table. | Record number—4-byte unsigned integer |
4 | Phase 1 end | The CHECKPOINT LOADING END request has successfully completed after the end of the acquisition phase. |
|
5 | Phase 2 begin | The EXEC MLOAD request is about to be sent to Teradata Database. | No data accompanies the phase 2 begin event code |
6 | Phase 2 end | Processing of the EXEC MLOAD request 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 | Teradata Database restart | Teradata MultiLoad received a crash message from Teradata Database or from the CLIv2. | No data accompanies the Teradata Database restart event code |
10 | CLIv2 error | Teradata MultiLoad received a CLIv2 error. | Error code—4-byte unsigned integer |
11 | Teradata Database error | Teradata MultiLoad received a Teradata Database error that will produce an exit code of 12. | Error code—4-byte unsigned integer Not all Teradata Database errors cause this event. For example, an Error 3807 while trying to drop or create a table does not terminate Teradata MultiLoad.
|
12 | Exit | Teradata MultiLoad is terminating. | Exit code—4-byte unsigned integer |
21 | AMPs down | Teradata Database has one or more down AMPs, just prior to the EXEC MLOAD statement. | No data accompanies the AMPs down event code |
22 | Import begin | The first record is about to be read for each import task. | Import number—4-byte unsigned integer |
23 | Import end | The last record has been read for each import task. The returned data is the record statistics for the import task. |
|
24 | Delete init. | Successful processing of a BEGIN DELETE MLOAD command |
|
25 | Delete begin | A DELETE statement is about to be sent to Teradata Database. |
|
26 | Delete end | Successful processing of the EXEC MLOAD request for a delete task |
|
27 | Delete exit | The end of a delete task | Exit code—4-byte unsigned integer |
28 | Phase 1 end 64 | The CHECKPOINT LOADING END request has successfully completed after the end of the acquisition phase. |
|
29 | Import end 64 | The last record has been read for each import task. The returned data is the record statistics for the import task. |
|
30 | Initialize EON | Successful processing of the NOTIFY option of the BEGIN MLOAD or BEGIN DELETE MLOAD command |
|
31 | Phase 1 begin EON | The beginning of the acquisition
phase It is called one time for each table specified in the BEGIN MLOAD or BEGIN DELETE. |
|
32 | Checkpoint 64 | Checkpoint information has been written to the restart log table | Record number—24-byte string |
33 | Phase 2 end 64 | Processing of the EXEC MLOAD request completed successfully. |
|
34 | Error table 1 64 | Processing of the SEL COUNT(*) request completed successfully for the second error table. |
|
35 | Error table 2 64 | Processing of the SEL COUNT(*)
request completed successfully for the second error table For each table specified in the BEGIN MLOAD command: |
|
36 | Delete init. EON | Successful processing of a BEGINDELETE MLOAD command |
|
37 | Delete begin EON | A DELETE statement is about to be sent to Teradata Database. |
|
38 | Delete end 64 | Successful processing of the EXEC MLOAD request for a delete task |
|