A job can be aborted by right-clicking the job in the Scheduler window and choosing Abort Job from the context menu.

Once in this state, a job cannot be restarted. The job now only exists as a log of what occurred and is no longer regarded as a job.

Effects of Aborting a Job

The effects of aborting a job depend on the Operating System the Scheduler is running on, the target platform, and the action being run.

Rolling back the current transaction may take a considerable amount of time.

Windows Scheduler

Greenplum (target)

Load and update processes are not stopped for all objects.

Hive (target)

Load and update processes are not stopped for all objects.

Netezza (target)

Load and update processes are not stopped for all objects.

PDW (target)

Object

Action

Effect

Load

Native Load, SSIS Load

Does not stop process

Load

ODBC Load, Database Link Load, File/Script Windows Load

Stops process

All objects using Procedures (Local targets)

Update

Stops process and rolls back current transaction

All objects using Procedures (remote targets)

Update

Does not stop process

Cube

Update

Does not stop process

Unix Scheduler

Hive (target)

File/Hadoop Load processes are not stopped on Hive target platforms.