Update Operator Events
Table 45 lists the event codes and describes the data that the Update operator passes to the notify exit routine for each event. The information in this table is also sent to the system log.
Note: To support future enhancements, always verify that your notify exit routines ignore invalid or undefined event codes, and that they do not cause the operator to terminate abnormally.
Event |
Event Code |
Event Description and Data Passed |
Initialize |
0 |
Signifies successful processing of the notify feature: |
Phase 1 Begin |
2 |
Signifies the beginning of the insert phase, where table name is specified by the DML statement: |
Checkpoint |
3 |
Signifies that checkpoint information is written to the restart log table: |
Phase 1 End |
4 |
Signifies the CHECKPOINT LOADING END request has successfully completed after the end of the acquisition phase: |
Phase 2 Begin |
5 |
Signifies that the application phase is beginning: |
Phase 2 End |
6 |
Signifies that the application phase is complete. For each table in the request: |
Error Table 1 |
7 |
Signifies that processing of the SEL COUNT(*) request completed successfully for the first error table. |
Error Table 2 |
8 |
Signifies that processing of the SEL COUNT(*) request completed successfully for the second error table. |
Teradata Database Restart |
9 |
Signifies that the Update operator received a crash message from the Teradata Database or from the CLIv2: |
CLIv2 Error |
10 |
Signifies that the Update operator received a CLIv2 error: |
Teradata Database Error |
11 |
Signifies that the Update operator received a Teradata Database error that will produce an Exit code of 12: 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 the Update operator. |
Exit |
12 |
Signifies that the Update operator is terminating: |
AMPs Down |
21 |
Signifies that the Teradata Database has one or more non-operational AMPs, just prior to the acquisition phase: |
Import Begin |
22 |
Signifies that the first record is about to be read for each import task: |
Import End |
23 |
Signifies that the last record is read for each import task. The returned data is the record statistics for the import task: |
Delete Init |
24 |
Signifies successful processing of a DELETE statement: |
Delete Begin |
25 |
Signifies that a DELETE statement is about to be sent to the Teradata Database: |
Delete End |
26 |
Signifies successful processing of a delete task: |
Delete Exit |
27 |
Signifies the end of a delete task: |
Checkpoint |
28 |
Signifies that checkpoint information is written to the restart log table: This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'. |
Phase I End |
29 |
Signifies the CHECKPOINT LOADING END request has successfully completed after the end of the acquisition phase: This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'. |
Import End |
30 |
Signifies that the last record is read for each import task. The returned data is the record statistics for the import task: This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'. |
Phase 2 End |
31 |
Signifies that the application phase is complete for each table in the request: This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'. |
Error Table 1 |
32 |
Signifies that processing of the SEL CAST(COUNT(*) AS BIGINT) request completed successfully for the first error table: This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'. |
Error Table 2 |
33 |
Signifies that processing of the SEL CAST(COUNT(*) AS BIGINT) request completed successfully for the first error table: This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'. |
Initialize |
34 |
Signifies successful processing of the notify feature: This event is only available when the value for the NotifyMethod attribute is set to 'ExitEON'. |
Phase 1 Begin |
35 |
Signifies the beginning of the insert phase, where table name is specified by the DML statement: This event is only available when the value for the NotifyMethod attribute is set to 'ExitEON'. |
Delete Begin |
36 |
Signifies that a DELETE statement is about to be sent to the Teradata Database: This event is only available when the value for the NotifyMethod attribute is set to 'ExitEON'. |
The following table lists events that create notifications. Some events create notifications only for import tasks, some only for delete tasks, and some for both.
Event |
Import Task |
Delete Task |
Notification Level |
Signifies |
||
Low |
Med |
High |
||||
Initialize |
x |
|
Yes |
Yes |
Yes |
Successful processing of the notify option |
Phase 1 Begin |
x |
|
No |
Yes |
Yes |
The acquisition phase is beginning |
Checkpoint |
x |
|
No |
No |
Yes |
Checkpoint information is written to the restart log table |
Phase 1 End |
x |
|
No |
Yes |
Yes |
Successful completion of the acquisition phase |
Phase 2 Begin |
x |
x |
No |
Yes |
Yes |
The application phase is beginning |
Phase 2 End |
x |
|
No |
Yes |
Yes |
Successful completion of the application phase |
Error Table 1 |
x |
|
No |
No |
Yes |
Successful processing of the SEL COUNT(*) request for the first error table |
Error Table 2 |
x |
x |
No |
No |
Yes |
Successful processing of the SEL COUNT(*) request for the second error table |
Teradata Database Restart |
x |
x |
No |
Yes |
Yes |
A crash error was encountered from the Teradata Database or CLIv2 that will terminate the load operation |
CLIv2 Error |
x |
x |
Yes |
Yes |
Yes |
A CLIv2 error was encountered |
Teradata Database Error |
x |
x |
Yes |
Yes |
Yes |
A Teradata Database error was encountered that will terminate the load operation |
Exit |
x |
|
Yes |
Yes |
Yes |
The Update operator is terminating |
AMPs Down |
x |
x |
No |
No |
Yes |
Non-operational AMPs on the Teradata Database |
Import Begin |
x |
|
No |
No |
Yes |
First record about to be read |
Import End |
x |
|
No |
No |
Yes |
Last record is read |
Delete Init |
|
x |
Yes |
Yes |
Yes |
The delete task is about to begin |
Delete Begin |
|
x |
No |
Yes |
Yes |
DELETE statement about to be sent to the Teradata Database |
Delete End |
|
x |
No |
Yes |
Yes |
Successful delete task processing |
Delete Exit |
|
x |
Yes |
Yes |
Yes |
End of delete task |