Evaluating Jobs with Exit Code=0
The job logs may contain the following important information, which is of value and may warrant further action.
Review the Metadata
Teradata PT provides two types of metadata.
TWB_STATUS private log captures job performance data at different stages of the job. Teradata PT also provides a tbuild command option for specifying the interval (in seconds) for collecting performance data. For about all tbuild options Teradata Parallel Transporter Reference.
This information is useful for evaluating the performance of a job in terms of throughput and the cost of exporting and loading of data by each operator. It is also useful for capacity planning by collecting the performance data for a period of time, summarizing the CPU utilization and elapsed time for each job, and then determining the trend of performance for the overall loading and exporting processes for a specific system configuration.
Here are some tips for performance evaluations and tuning:
The source and target data shown in this log is for reference only, and requires no specific usage strategy.
Review the Warnings
Check for any minor warnings that may appear in the logs to see if further action is required, as shown in the following examples:
Action: Review the warnings and associated errors. Determine whether or not ignoring the error is achieving the results you expected. Reset the ErrorList attribute if required.
Action: Review the error message output and correct the problems as you would any normal operating system error messages. If the OS Command operator IgnoreError attribute value was set to Yes, then any command errors would not have terminated the job. In these cases, look at the logs for any OS Command operator error messages and if any are present, determine whether or not later job steps were adversely affected by any commands that were not successfully executed.
When data is being written to the Teradata Database, consumer operators can be set to allow the job to proceed even if some data cannot be loaded, using the ErrorLimit attribute. This attribute applies to the following operators:
There may be various reasons why the data did not load, but it is often due to violations of the schema or data type requirements when the data was originally entered into the source files.
For more information, refer to the sections on Load, Stream, and Update operator errors in Chapter 11: “Troubleshooting.”