Load Operator Events - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2436
lifecycle
previous
Product Category
Teradata Tools and Utilities

Load Operator Events

Table 43 lists the event codes and describes the data that operators pass to the notify exit routine and the system log for each event.

Note: To support future enhancements, always verify that notify exit routines ignore invalid or undefined event codes, and that they do not cause the operator to terminate abnormally.

 

Table 43: Load Operator Notify Event Codes 

Event

Event Code

Event Description and Data Passed To The Notify Exit Routine

Initialize

0

Signifies successful processing of the notify feature:

  • Version ID length—4-byte unsigned integer
  • Version ID string—32-character (maximum) array
  • Operator ID—4-byte unsigned integer
  • Operator name length—4-byte unsigned integer
  • Operator name string—32-character (maximum) array
  • User name length—4-byte unsigned integer
  • User name string—64-character (maximum) array
  • Optional string length—4-byte unsigned integer
  • Optional string—80-character (maximum) array
  • Operator handle—4-byte unsigned integer
  • Phase 1 Begin

    2

    Signifies the beginning of the insert phase, where the table name is specified by the INSERT statement:

  • Table name length—4-byte unsigned integer
  • Table name—128-character (maximum) array
  • Checkpoint

    3

    Signifies that checkpoint information is written to the restart log table:

  • Record number—4-byte unsigned integer
  • Phase 1 End

    4

    Signifies the CHECKPOINT LOADING END request has successfully completed after the end of the insert phase:

  • Records read—4-byte unsigned integer
  • Records sent to the Teradata Database—4-byte unsigned integer
  • Phase 2 Begin

    5

    Signifies that the application phase is beginning:

  • No data accompanies the phase 2 begin event code
  • Phase 2 End

    6

    Signifies that the application phase is complete:

  • Records loaded—4-byte unsigned integer
  • Error Table 1

    7

    Signifies that processing of the SEL COUNT(*) request completed successfully for the first error table:

  • Number of rows—4-byte unsigned integer
  • Error Table 2

    8

    Signifies that processing of the SEL COUNT(*) request completed successfully for the second error table:

  • Number of rows—4-byte unsigned integer
  • Teradata Database Restart

    9

    Signifies that the Load operator received a crash message from the Teradata Database or from the CLIv2:

  • No data accompanies the Teradata Database restart event code
  • CLIv2 Error

    10

    Signifies that the Load operator received a CLIv2 error:

  • Error code—4-byte unsigned integer
  • Teradata Database Error

    11

    Signifies that the Load operator received a Teradata Database error that will produce an Exit code of 12:

  • Error code—4-byte unsigned integer
  • Exit

    12

    Signifies that the Load operator is terminating:

  • Exit code—4-byte unsigned integer
  • Checkpoint

    13

    Signifies that checkpoint information is written to the restart log table:

  • Record number—8-byte unsigned integer
  • This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'.

    Phase 1 End

    14

    Signifies the CHECKPOINT LOADING END request has successfully completed after the end of the insert phase:

  • Records read—8-byte unsigned integer
  • Records sent to the Teradata Database—8-byte unsigned integer
  • This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'.

    Phase 2 End

    15

    Signifies that the application phase is complete:

  • Records loaded—8-byte unsigned integer
  • This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'.

    Error Table 1

    16

    Signifies that processing of the SEL CAST(COUNT(*) AS BIGINT) request completed successfully for the first error table:

  • Number of rows—8-byte unsigned integer
  • This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'.

    Error Table 2

    17

    Signifies that processing of the SEL CAST(COUNT(*) AS BIGINT) request completed successfully for the second error table:

  • Number of rows—8-byte unsigned integer
  • This event is only available when the value for the NotifyMethod attribute is set to 'Exit64' or 'ExitEON'.

    Initialize

    18

    Signifies successful processing of the notify feature:

  • Version ID length—4-byte unsigned integer
  • Version ID string—pointer to a null-terminated string
  • Operator ID—4-byte unsigned integer
  • Operator name length—4-byte unsigned integer
  • Operator name string—pointer to a null-terminated string
  • User name length—4-byte unsigned integer
  • User name string—pointer to a null-terminated string
  • Optional string length—4-byte unsigned integer
  • Optional string—pointer to a null-terminated string
  • Operator handle—4-byte unsigned integer
  • This event is only available when the value for the NotifyMethod attribute is set to 'ExitEON'.

    Phase 1 Begin

    19

    Signifies the beginning of the insert phase, where the table name is specified by the INSERT statement:

  • Table name length—4-byte unsigned integer
  • Table name—pointer to a null-terminated string
  • This event is only available when the value for the NotifyMethod attribute is set to 'ExitEON'.

    Table 44 lists events that create notifications.

     

    Table 44: Load Operator Events That Create Notifications 

    Event

    Notification Level

    Signifies

    Low

    Med

    High

    Initialize

    Yes

    Yes

    Yes

    Successful processing of the notify option

    Phase 1 Begin

    No

    Yes

    Yes

    The acquisition phase is beginning

    Checkpoint

    No

    No

    Yes

    Checkpoint information is written to the restart log table

    Phase 1 End

    No

    Yes

    Yes

    Successful completion of the acquisition phase

    Phase 2 Begin

    No

    Yes

    Yes

    The application phase is beginning

    Phase 2 End

    No

    Yes

    Yes

    Successful completion of the application phase

    Error Table 1

    No

    No

    Yes

    Successful processing of the SEL COUNT(*) request for the first error table

    Error Table 2

    No

    No

    Yes

    Successful processing of the SEL COUNT(*) request for the second error table

    Teradata Database Restart

    No

    Yes

    Yes

    A crash error was encountered from the Teradata Database or CLIv2

    CLIv2 Error

    Yes

    Yes

    Yes

    A CLIv2 error was encountered

    Teradata Database Error

    Yes

    Yes

    Yes

    A Teradata Database error was encountered that will terminate the load operation

    Exit

    Yes

    Yes

    Yes

    The Load operator is terminating