Required and Optional Attributes - Parallel Transporter

If omitted, it defaults to the account identifier of the immediate owner database.

• 'None' = allows the Update job to start, restart, or continue as long as no more than one AMP is down in a cluster.
• 'Apply' = inhibits the Update operator job from entering or exiting the application phase when an AMP is down (default).
• 'All' = pauses the Update operator job when an AMP is down.

The output buffer size and the size of the rows in the Update table determine the maximum number of rows that can be included in each parcels to the Teradata Database. A larger buffer size reduces processing overhead by including more data in each parcels.

Allowable values are 1 through 16384, but if you specify a value of 16384, the actual buffer size gets set to 16775552 bytes, which is less than the full 16MB. If the value less than 1, an error message results and job terminates.

The default buffer size is 1024Kbytes. The maximum allowed buffer size is usually 16384 Kbytes. Values are evaluated when the connection to the Teradata Database is made.

If the supplied buffer size is too large, the operator scales it back to the maximum allowed buffer size.

The CheckpointRowCount values are:

• 'No' ('N') = The Update operator will not output rows sent at checkpoint(s) (default);
• 'Yes' ('Y') = The Update operator will output rows sent at checkpoint(s)

This attribute is only available in the TPT script mode.

Valid values are:

• ‘On’ = all SQL requests, responses, and data are encrypted.
• ‘Off’ = no encryption occurs (default).

• 'integerDate' = the integer DATE data type (default)
• 'ansiDate' = the ANSI fixed-length CHAR(10) DATE data type

The valid values for option are:

• 'Yes' (or 'Y') = perform the delete task. The delete task will know whether to retrieve a row based on whether the APPLY statement has a SELECT section in it.
• 'No' (or 'N') = do not perform the delete task (default).

Specifying any other value results in an error.

The absence of any value is the same as a 'No' value, that is, the Update operator will execute an IMPORT task, and none of the above rules apply.

If the DeleteTask attribute processing is enabled, the only other optional attributes with any importance are:

• TenacityHours
• TenacitySleep
• AmpCheck

Valid values are:

• ‘Yes’ = Update operator will drop the error table only if empty (default). Teradata PT automatically executes a DROP TABLE statement.

  If you run many update jobs on a regular basis, checking ‘Yes’ would cause lots of updates to the Data Dictionary, resulting in performance problems.

• ‘No’ = Update operation will not drop the error table, even if empty. The user must manually execute a DROP TABLE statement on the error table.

  If the tables are not dropped prior to running a Teradata PT job that would use tables by the same name, running that job may result in a DBS error or in unpredictable results.

Valid values are:

• ‘Yes’ = Update operator will drop the restart log table (default). Teradata PT automatically executes a DROP TABLE statement.

  If you run many update jobs on a regular basis, checking ‘Yes’ would cause lots of updates to the Data Dictionary, resulting in performance problems.

• ‘No’ = Update operation will not drop the restart log table. The user must manually execute a DROP TABLE statement on the restart log table.

  If the table is not dropped prior to running a Teradata PT job that would use the table by the same name, running that job may result in a DBS error or in unpredictable results.

Valid values are:

• ‘Yes’ = Update operator will drop the work table (default). Teradata PT automatically executes a DROP TABLE statement.

  If you run many update jobs on a regular basis, checking ‘Yes’ would cause lots of updates to the Data Dictionary, resulting in performance problems.

• ‘No’ = Update operation will not drop the work table. The user must manually execute a DROP TABLE statement on the work table.

  If the tables are not dropped prior to running a Teradata PT job that would use tables by the same name, running that job may result in a DBS error or in unpredictable results.

This number is approximate because the Update operator sends multiple rows of data at a time to the Teradata Database. By the time the Update operator processes the message indicating that the error limit has been exceeded, it may have loaded more records into the error table than the actual number specified in the error limit.

The ErrorLimit specification must be greater than 0. Specifying an invalid value will cause the Update operator job to terminate. By default, ErrorLimit value is unlimited.

The ErrorLimit specification applies to each instance of the Update operator.

This must be a new table name. You cannot use a name that duplicates the name of an existing table unless you are restarting a paused Update operator job.

This must be a new table name. Do not use a name that duplicates the name of an existing table unless you are restarting an Update operator job.

Valid options are:

• 'Yes' = output the full SQL to the log. The maximum length is 1M.
• 'No' = do not output SQL to the log.
• No value or attribute omitted = accept the pre-defined limit, which displays up to 32K of SQL if all of the SQL is less than 32K. If the SQL to be logged exceeds 32K, truncate the display to the first 32K bytes.

If running a new job, specify a new table name that is different from the name of any existing table. The Update operator then creates a new restart log table.

If restarting a paused job, then the restart log table must exist, and the Update operator restarts the job from the last checkpoint. The restarted job will continue using the existing restart log table.

When a job successfully completes, the operator drops the restart log table. Failure to specify a restart log table will cause the job to terminate.

The following privileges are required on the restart log table:

• SELECT
• INSERT
• DELETE

The following privileges are required on the database that contains the restart log table:

• DROP
• CREATE

The Update operator automatically maintains the restart log table. Manipulating the restart log table in any way invalidates the restart capability.

If the restart log table name is not fully qualified, it is created under the user's default (logon) database. If the WorkingDatabase attribute is used, you MUST fully qualify the restart log table name, even if the restart log table is going to reside in the default (logon) database.

The MaxSessions value must be greater than 0. Specifying a value less than 1 terminates the job.

The default is one session per available AMP. The maximum value cannot be more than the number of AMPS available.

The main instance calculates an even distribution of the Update operator sessions among the number of instances. For example, if there are 4 instances and 16 Update operator sessions, then each instance will log on four Update operator sessions.

The MinSessions value must be greater than 0 and less than or equal to the maximum number of Update operator sessions. Specifying a value less than 1 (the default) terminates the job.

• libnotfyext.dll for Windows platforms
• libnotfyext.dylib for the Apple OS X platform
• libnotfyext.so for all other UNIX platforms
• NOTFYEXT for z/OS platforms

See Deprecated Syntax for information about providing your own notify exit routine.

• 'Yes' (or 'Y') = notify exit routine is built as a DLL (default).
• 'No' or ('N') = notify exit routine is not built as a DLL.

Specifying any other value terminates the job.

• 'Off' = no notification of events is provided (default)
• 'Low' = 'Yes' in the Low Notification Level column
• 'Med' = 'Yes' in the Medium Notification Level column
• 'High' = 'Yes' in the High Notification Level column

• 'None' = no event logging is done (default).
• 'Msg' = sends the events to a log.
  • On Windows, the events are sent to the event log that can be viewed using the Event Viewer. The messages are sent to the application log.
  • On Solaris, AIX, and HP-UX platforms, the destination of the events depends on the setting specified in the /etc/syslog.conf file.
  • On SLES11, the destination of the events is dependent upon the setting specified in the /etc/syslog-ng.conf file.
  • On z/OS systems, events are sent to the job log.
• 'Exit' = sends the events to a user-defined notify exit routine. Row count information is in 4-byte unsigned integer values.
• 'Exit64' = sends the events to a user-defined notify exit routine. Row count information is in 8-byte unsigned integer values for these events:
  • NMEventCheckPoint64
  • NMEventPhaseIEnd64
  • NMEventImportEnd64
  • NMEventPhaseIIEnd64
  • NMEventErrorTableI64
  • NMEventErrorTableII64
• 'ExitEON' = sends the events to a user-defined notify exit routine.

  Complete Teradata object names are passed to the notify exit routine for these events:

  • NMEventInitializeEON
  • NMEventPhaseBeginEON
  • NMEventDeletesBeginEON

  In addition ExitEON sends row count information in 8-byte unsigned integer values.

The maximum length of the string is:

• 80 bytes, if the NotifyMethod is 'Exit'
• 16 bytes, if NotifyMethod is 'Msg'

Valid values are 1 through 16383. The default value is 16383.

The pack factor applies only when the job uses the extended MultiLoad protocol.

The pack factor tells the Update operator how many data records to include with the Array Insert statement. The Array Insert statement is sent to the Teradata Database during the job acquisition phase.

• 'Yes' (or 'Y')= pause the Update operator job after the acquisition phase.
• 'No' (or 'N') = do not pause (default).

Specifying any other value terminates the job.

The absence of any value for the PauseAcq attribute means that the Update operator job will execute both the acquisition phase and the application phase without pausing.

The private log can be viewed using the tlogview command as follows, where jobId is the Teradata PT job name and privateLogName is the value for the Update operator PrivateLogName attribute:

tlogview -j jobid -f privatelogname

By default, no diagnostic trace messages are produced. Diagnostic trace messages are produced only when the user sets a valid value for the TraceLevel attribute.

If the private log is not specified, all of the output is stored in the public log.

For more information about the tlogview command, see Teradata PT Utility Commands.

The queryBandExpression is a set of name=value pairs, separated by a semicolon and ending with a semicolon. The user defines the Query Band expression, which will look similar to the following example:

‘org=Finance;load=daily;location=west;’

QueryBandSessInfo may also be specified as an ARRAY attribute.

For information on the rules for creating a Query Band expression SQL Data Definition Language Syntax and Examples (B035-1144) and SQL Data Definition Language Detailed Topics (B035-1184).

The value of the QueryBandSessInfo attribute is displayed in the Update Operator private log.

Use of the QueryBandSessInfo attribute is subject to the following rules:

• By default, Query Band is off until a valid value appears for the QueryBandSessInfo attribute.
• If the QueryBandSessInfo attribute contains a value, the Update operator constructs the necessary SET QUERY BAND SQL and issues it as part of the Update operator SQL sessions to communicate the request to the Teradata Database.
• The Update operator does not check the Query Band expression, but passes the expression to Teradata Database as is.
• If the version of Teradata Database against which the job is being run does not support the Query Band feature, no Query Banding will take place. However, the operator will ignore the error and run the rest of the job.
• If there is a syntax error in the Query Band expression, Teradata Database will return an error. The Update operator will then terminate the job and report the error to the user.

Valid values:

• ‘On’ = override normal replication services controls for the active session.
• ‘Off’ = override of normal replication services is turned off for the active session (when change data capture is active).
• ‘None’ = no override request is sent to the Teradata Database (default).

For more information, see Teradata Replication Services Using Oracle GoldenGate (B035-1152).

The table must already exist.

Valid values are:

• 'Yes' or ‘Y’ = Enable FastFail feature. The job will terminate gracefully when it is supposed to be held by DBS.
• 'No' or ‘N’ = FastFail feature is not enabled (default). The job will appear to hang if the TASM rules dictate that a job should be held for any reason.

The default value is 4 hours. To enable the tenacity feature, the hours value must be greater than 0. Specifying a value of 0 disables the tenacity feature. Specifying a value of less than 0 terminates the Update job.

The minutes value must be greater than 0. If you specify a value less than 1, the Update operator responds with an error message and terminates the job. The default is 6 minutes.

The dbcName can be up to 256 characters and can be a domain server name.

If you do not specify the value for the TdpId attribute, the operator uses the default TdpId established for the user by the system administrator.

The trace levels are:

• 'None' = TraceLevel turned off (default).
• 'CLI' = enables the tracing function for CLI-related activities (interaction with the Teradata Database)
• 'PX' = enables the tracing function for activities related to the Teradata PT infrastructure
• 'Oper' = enables the tracing function for operator-specific activities
• 'Notify' = enables the tracing of activities related to the Notify feature
• 'All' = enables tracing for all of the above activities

The VARCHAR ARRAY can specify more than one value, for example:

VARCHAR TraceLevel = 'CLI'
VARCHAR TraceLevel = 'OPER'
VARCHAR ARRAY TraceLevel = [ 'CLI' ]
VARCHAR ARRAY TraceLevel = [ 'CLI', 'OPER' ]

The TreatDBSRestartAsFatal values are:

• ‘No’ (‘N’) = The operator will not terminate if a Teradata Database restart occurs (default). The Teradata Database restart will be treated as a retryable one.
• ‘Yes’ (‘Y’) = The operator will terminate if a Teradata Database restart occurs.

Valid values:

• 'On' = Enable the Unicode Pass Through feature in the operator.
• 'Off' = (Default) Disable the Unicode Pass Through feature in the operator.

This must be a new table name that does not duplicate the name of any existing table, unless you are restarting a paused Update operator job.