Logging Levels - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

You can control the level of logging for a job that you launch through the command-line interface. For the command-line interface, use the -log_level parameter of the create and move commands. We recommend using log level 0 or 1 during normal operation.

Value Command-Line Interface Description Details
0 x Disables logging. This is the default value for the -log_level parameter of the create and move commands.
  • If the job completes successfully, the log is deleted.

    You cannot view utility logs of successfully completed jobs with the status or view_log commands.

  • If the job fails, the log is not deleted.

    You can view the logs of the failed job with the status or view_log commands.

1 x Enables detailed logging. You can view the logs of successfully completed or failed jobs with the status or view_log commands.
2 x Enables extra logging for command-line interface jobs that use Teradata ARC by setting the VERBOSE option of Teradata ARC. You can view the logs of successfully completed or failed jobs with the status or view_log commands.
99 x Enables maximum logging.
  • For TPT API, both operator and data stream logs are sent to /var/opt/teradata/datamover/logs/temp/task XXX YYYY directory, where XXXX is the job id and YYYY is the task ID.
  • For ARC jobs, this sets the VERBOSE3 option.
  • For Aster jobs, this sets TRACE_LEVEL-VALUE=7, when calling the AsterSQLMR functions.

You can view the logs of successfully completed or failed jobs with the status or view_log commands.

Use log level 99 only under the guidance of a Teradata Technical Support Specialist when a job issue needs extremely detailed debug information.

If you enable maximum logging, Data Mover creates temporary directories on the Data Mover Agent server that executes the task. These directories are not automatically deleted. When you no longer need them, delete the task_XXXX_YYYY directories in /var/opt/teradata/datamover/logs/temp.