| 0 |
x |
Disables logging. This is the default value for the -log_level parameter of the create and move commands. |
|
| 1 |
x |
Enables detailed logging. |
- You can view the logs of successfully completed or failed jobs with the status command.
- If a DSA job, this enables the DSMAIN error logging level. DSMAIN logs are in the /var/opt/teradata/tdtemp/bar directory on the source and target databases.
|
| 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 command.
- If a DSA job, this enables the DSMAIN info logging level. DSMAIN logs are in the /var/opt/teradata/tdtemp/bar directory on the source and target databases.
- The DSA job definition is logged in the Data Mover agent log as a JSON.
|
| 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 DSA jobs, this enables the DSMAIN DEBUG logging level. DSMAIN logs are under the /var/opt/teradata/tdtemp/bar directory on the source and target databases.
- 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 command.
- 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 runs 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.
- If a DSA job, the DSA job definition is logged in the Data Mover agent log as a JSON.
|