Resetting a job

If a job has stopped or aborted, it is difficult to determine whether all the required data was written to the target data tables. You can reset a job or job invocation.

About this task

When a job has a status of Stopped or Aborted, you must reset it before running the job again.

By resetting a job, you set it back to a runnable state and, optionally (on server jobs only), return your target files to the state they were in before the job was run.

Note: You can only reinstate server job sequential files and hashed files to a pre-run state if the backup option has been chosen on the corresponding stage in the job design.

If you want to undo the updates performed during a successful job, you can also use the Reset command for jobs with a status of Finished. The Reset command is not available for jobs with a status of Not compiled or Running.

Procedure

Select the job or invocation you want to reset in the Job Status view.
Choose Job > Reset or click the Reset button on the toolbar. A message box appears.
Click Yes to reset the tables. All the files in the job are reinstated to the state they were in before the job was run. The job's status is updated to Has been reset.
Note: It might take some time for the job status to be updated, depending on the load on the engine tier host and the refresh rate for the client.