Considerations for Aborting a Job | Command Line | Teradata DSA - 17.20 - Considerations for Aborting a Job - BAR - Data Stream Architecture

Teradata® DSA User Guide

Product
BAR
Data Stream Architecture
Release Number
17.20
Published
November 2022
Last Update
2022-11-14
Content Type
User Guide
Publication ID
B035-3150-101K
Language
English (United States)
Last Update
2022-11-14
Reasons to abort a job after it has been submitted include:
  • You forgot to include an object for backup in the job definition XML file.
  • You see that data will fill the media if the job is completed.
If you abort a restore job of a DSC repository backup while the job is in progress, the DSC metadata is corrupted. DSC triggers a command to restore all repository tables to their initial state, which is an empty table. The current data in the DSC repository is lost and must be recovered using disaster recovery.

You can use the abort_job command to abort an actively running job or a job in the queue. An abort command creates two states for the job. While the job state is aborting, devices are being released for other jobs to use. After the job has reached an aborted state, the job releases DSA stream resources and the DSC job slot.

If you abort an actively running job, DSA does not create a save set. Any backed up files are rolled back to the state they were in following the last complete, successful run. Third-party backup management software does not keep records of jobs that are not run successfully.