Optional Attributes - Parallel Transporter

• The output buffer size and the size of the rows in the Load table determine the maximum number of rows included in each parcel to the database. A larger buffer size reduces processing overhead by including more data in each parcel.
• 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.
• The default buffer size is the maximum size allowed, which depends on the database and CLI version. The maximum allowed buffer size is usually 16384K bytes.
• If you specify a value less than one, the Load driver issues an error message and terminates the job. Any other value specified is evaluated when the connection to the database is made. Because some Teradata Database versions support buffer sizes of 32K only, specifying a value of 64K would be invalid, but the driver does not know this until it connects to the database and queries its version.
• If the supplied buffer size is too large, the Load driver scales it back to the maximum allowable size.

In a multi-instance environment, the main and all the worker instances must have the same session character set. Also, the data for each instance must be in the same character set as the session character set. If the main instance does not use the TD_CHARSET attribute, then the worker instances should not use the attribute. If the main instance specifies a different session character set than any of its worker instances, then the Load, Export, and Update drivers will use the main instance’s session character set for the entire job. The Stream driver, however, will let each instance use its own session character set for the job.

Also, note that the session character set for all instances should not change if a restart occurs. If any instance specified a value for TD_CHARSET before the restart then that instance needs to specify the same value for TD_CHARSET when the connection is initiated again and then restarted.

Starting in TTU 17.10, Teradata PT supports the Connection String feature. A connection string allows Teradata PT to pass various parameters and associated values to CLIv2 without the need to implement individual operator attributes for each parameter.

This enhancement allows Teradata PT to support a variety of features, one of which is the Transport Layer Security (TLS) feature.

The Teradata PT operator will not parse or validate the contents of the connection string. The connection string is passed as is to CLIv2. Any errors in the connection string will be provided by CLIv2.

For a list of valid parameters and associated values, see Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems, B035-2418.

• Off = No encryption occurs. This is the default setting.
• On = All SQL requests, responses, and data are encrypted.

• IntegerDate = Integer DATE data type. This is the default setting.
• AnsiDate = ANSI fixed-length CHAR(10) DATE data type.

If the error tables are not dropped at the end of a successfully terminating job and the same error table names are used in a subsequent Load job then the database returns an error on those subsequent Load jobs, even if those error tables are empty.

If the restart log table is not dropped at the completion of a successful job and the same restart log table name is provided in a subsequent Load job then the results will be unpredictable. This unpredictability is due to the nature of the Teradata FastLoad protocol, where the existence of a restart log table implies the job is a restart and the Load driver may attempt to restart the job at a point in time as dictated by the contents of the restart log table.

The Load driver tries to detect whether this situation has occurred and will attempt to terminate the job with a meaningful error message but this attempt is dependent upon the contents of the restart log table.

• Specifying an invalid value causes the Load driver to terminate. By default, ErrorLimit value is unlimited.
• The ErrorLimit specification must be greater than zero.

• ErrorTable1 is for containing records rejected during the acquisition phase of the Load driver job because of:
  • Data conversion errors
  • Constraint violations
  • AMP configuration changes
• The default name for ErrorTable1 is ttname_ET.

For more information on the error table format and the procedure to correct errors, see “FastLoad Errors” in Teradata® FastLoad Reference, B035-2411.

• ErrorTable2 contains records that violated the unique primary index constraint.
• These types of errors occur during the acquisition phase of the Load driver job.
• The default name for ErrorTable2 is ttname_UV.

For more information on the error table format and the procedure to correct errors, see “FastLoad Errors” in Teradata® FastLoad Reference, B035-2411.

• See your site security administrator for specific mechanism names. For a list of available mechanisms, see Teradata Vantage™ - Analytics Database Security Administration, B035-1100.
• The job terminates if the attribute exceeds eight bytes.

See your site security administrator for specific mechanism data. For more information, see Teradata Vantage™ - Analytics Database Security Administration, B035-1100.

• The default is one session per available AMP. The maximum value cannot be more than the number of AMPS available.
• The MaxSessions value must be greater than one. Specifying a value less than one terminates the job.
• The MaxSessions value must be greater than or equal to the value of TD_MAX_INSTANCES.

• The default is one session.
• The MinSessions value must be greater than zero and less than or equal to the maximum number of Load driver sessions. Specifying a value less than one terminates the Load driver.

For more information on the Notify feature, see “Load Operator” in Teradata® Parallel Transporter Reference, B035-2436.

a=1;b=2;c=3;d=4;

If the TD_QUERY_BAND_SESS_INFO is set, the following request will be sent by every SQL session connected by the Teradata PT Load driver:

SET QUERY_BAND =’<User-Defined Query Band Expression>’ FOR SESSION;

Setting the TD_QUERY_BAND_SESS_INFO attribute in jobs running against non-supported versions of Teradata Database causes a non-fatal error. No error code is returned to the user during initiation and the job is allowed to proceed. The log table will not be dropped at the end of the job and the TD_Evt_ExitCode event returns a warning value of four instead of the normal success value of zero if queried. In this case, error information can be found in the trace file.

The value for the attribute needs to be provided by the user, and the operator will prepend the hard-coded string SET ROLE . For more information, see Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.

• The dbcname can be up to 256 characters and can be a domain server name.
• TDP stands for Teradata Director Program and is specified for mainframe z/OS platforms.
• If you do not specify the value for the TdpId attribute, the driver uses the default TdpId established for the user by the system administrator.

• The default value is four hours. To make the tenacity feature available, the hours value must be greater than zero.
• Specifying a value of zero will disable the tenacity feature.
• Specifying a value of less than zero terminates the Load driver.

• The minutes value must be greater than zero. If you specify a value less than one, the Load driver responds with an error message and terminates the job.
• The default is six minutes.

When you provide a value for this attribute, the operator will build the "SET TIME ZONE <timeZoneValue>;" SQL request.

The operator will send the request to the database on the main control and auxiliary SQL sessions after the sessions are connected.

The operator does not send the request on the FastLoad protocol sessions, because the database does not allow the request to be sent on the FastLoad protocol sessions.

For more information on the SET TIME ZONE SQL attribute, see Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.

Use the AddArray attribute method to specify the two types of tracing levels: driver tracing and infrastructure tracing.

TD_OFF is the default setting for both driver tracing and infrastructure tracing. No external log file is produced unless this default is changed. Specifying TD_OFF for both driver tracing and infrastructure tracing is the same as disabling tracing.

If the TraceLevel is set to any value other than TD_OFF, an external log file is created for each instance of the driver.

The trace levels for infrastructure tracing should only be used when you are directed to by Teradata support. TD_OFF, which disables infrastructure tracing, should always be specified.

The default setting creates a new file name using the name of the driver followed by a time stamp.

• ST_GEOMETRY
• XML
• JSON
• DATASET

When a value is provided for this attribute, the operator builds the "SET TRANSFORM GROUP FOR TYPE <tranformgrouValue>;" SQL request.

The operator sends the request to the database on the SQL session, after the session is complete.

If you set this attribute to Yes and a valid fully supported INSERT statement already exists, an error results.

To be valid, the table name must match the name of the table used in the TargetTable attribute and a semicolon must be the last non-space character in the supplied DML statement as follows:

INS[ERT] [INTO] <tablename>;