15.10 - Evaluating Jobs with Exit Code=4 - Parallel Transporter

Teradata Parallel Transporter User Guide

prodname
Parallel Transporter
vrm_release
15.10
category
User Guide
featnum
B035-2445-035K

Evaluating Jobs with Exit Code=4

When the job exit code=4, all the observables for Exit Code=0 still apply. In addition, the job may have encountered one or more serious warnings of the following types:

  • tbuild-based warnings
  • job script-based warnings
  • Unnecessary tbuild Command Option

    Teradata PT returns a warning message when the tbuild -s option, normally used to start a job from an intermediate step, directs the job to start at the first step (where the job would start without the -s option). The message is issued in case you had not meant to start at step one.

    Cause: Unnecessary tbuild command option

    Corrective Action:

  • Do not use tbuild -s unless you intend to start a job from an intermediate step.
  • If the job was supposed to start at an intermediate step, and starting at step one was an accident, examine the job logs to see if starting at step one caused any problems.
  • Invalid Value for a tbuild Command Option

    If the tbuild -h option specifies an invalid value for shared memory size, Teradata PT issues a warning identifying the size of shared memory it will actually use.

    Cause: The tbuild command specified an invalid value for -h.

    Corrective Action: For suggestions on how to correctly specify shared memory size the Teradata Tools and Utilities installation guide for your platform.

    Truncated Data

    If the values of source CHAR or VARCHAR columns could be, or will be, truncated when applied to the corresponding target columns, Teradata PT returns a warning message for each such column.

    Cause: Possible mismatched source and target schema definitions in the job script.

    Corrective Action: If the truncation is not acceptable, examine and adjust the source and target schemas to eliminate the mismatch that caused the truncation(s). Normally this requires ensuring that the schema for the target column (maximum) length is at least as large as the schema for the source column (maximum) length.

    Bad Source Data

    The DataConnector operator may encounter bad data in the source file. If the RecordErrorFileName attribute (previously known as “RowErrFileName,” which will no longer be used in documentation as of the next release), specifies a file name, the bad data will be sent to the file and the job allowed to proceed.

    Cause: Bad Source data.

    Corrective Action: Clean up the data and enter it manually in target table to complete the job.

    Note: For a list of obsolete syntax, which are supported but no longer documented, see Appendix B in the Teradata Parallel Transporter Reference.

    Delete Task with More than One Row

    This error depends on the following job scenario: The Update operator is set to delete data from a Teradata Database, with the DeleteTask attribute is set to a Y[es] value, but the deletion is triggered by a WHERE clause in the DELETE statement that is incomplete without some external data. The source of this data must be a single row on the source data stream.

    In this case the Update operator is only looking for one row as the trigger. If it sees more than one row in the data stream, Teradata PT will issue a warning.

    Cause: More than one row exists in the data stream.

    Corrective Action: Check to see why the Producer operator is sending more than one row to the data stream, as it may result in a more serious problem in a later run of the job.

    Ignore Unsupported Large Decimal in Teradata Database or CLI

    When you specify a valid value for the IgnoreMaxDecimalDigits attribute and the IgnoreMaxDecimalDigits attribute is set to Yes, the job will proceed even if Teradata Database or CLI does not support the Large Decimal feature, but it will issue a warning that indicates the mismatch in decimal support.

    Note: If the IgnoreMaxDecimalDigits is set to No, the job example above will abort with a fatal error.

    The MaxDecimalDigits and IgnoreMaxDecimalDigits attributes apply only to the following operators:

  • Export
  • SQL Selector
  • Cause: The user requested to continue the job when the Teradata Database or CLI does not support the Large Decimal feature.

    Corrective Action: None

    Paused Job

    When the PauseAcq attribute for the Load or Update operator is set to a Yes value, the job is paused after the completion of the acquisition phase, that is, when all the data in the file has been read. This protocol is often used for scripts that empty a data file periodically, for instance, once a day. The warning is only a reminder that the job has paused. Re-launch the job again when the file contains more data.

    Cause: User requested the job to pause after the completion of the acquisition phase.

    Corrective Action: None.

    Unsupported Query Band in Teradata Database

    When a value is specified for the QueryBandSessInfo attribute, the job proceeds even if Teradata Database does not support the Query Band feature.

    The QueryBandSessInfo attribute applies only to the following operators:

  • DDL
  • Export
  • Load
  • SQL Inserter
  • SQL Selector
  • Stream
  • Update
  • Cause: The version of the Teradata Database does not support the Query Band feature.

    Corrective Action: If you want to use the Query Band feature, change the TdpId attribute value to a Teradata Database that supports the Query Band feature.