You can pause and resume an archive job during the delete from source step when the following conditions are true:

The source is an Oracle database.
The entity tables include primary key constraints.
The source connection uses staging and uses the Oracle row ID for deletion.
The source connection does not use Oracle parallel DML for deletion.

You may want to pause a job during the delete from source step if you delete from a production system and you only have a limited amount of time that you can access the system. If the job does not complete within the access time, you can pause the job and resume it the next time you have access.

When the job pauses depends on the delete commit interval and the degree of parallelism configuration for the archive source. The pause occurs at the number of threads multiplied by the commit interval. When you pause the job, each thread completes the number of rows in the current commit and then pauses. The job pauses after all threads complete the current number of rows in the commit interval.

For example, if you configure the source to use a delete commit interval of 30,000 and two delete parallel threads, then the job pauses after the job deletes 60,000 rows. The job writes a message to the log that the threads are paused.

You can pause the job when you monitor the job status. When you expand the delete from source step, you can click on a link to pause the job. You can resume the job from the step level or at the job level. When you resume the job, the job continues at the point from which you paused the job. The log indicates when the threads pause and resume.