Aborting an application ingestion and replication job
You can abort an application ingestion and replication job of any load type that is in the Up and Running, Running with Warning, On Hold, or Stopping status.
You can abort an application ingestion and replication job from the My Jobs page in the Data Ingestion and Replication service or from the All Jobs tab on the Data Ingestion and Replication page in Operational Insights.
When you abort an incremental load job, Application Ingestion and Replication records an identifier for the position in the change stream where it has stopped the incremental processing. The identifier is stored in a recovery table named INFORMATICA_CDC_RECOVERY on the target. If you restart the job, Application Ingestion and Replication uses this identifier to identify the last change record that was loaded to the target and starts loading the changes that were made after that point in the change stream.
For initial load jobs, the subtasks that are already running stop immediately, and then the job stops. The subtasks that are not running remain in their current states.
On the Actions menu for the job that you want to abort, select Abort.
The status of the job changes to Aborting and then changes to Aborted.
For initial load jobs, the status of the subtasks that were running change to Aborted. For incremental load jobs, the status of the subtasks change to Stopped.
On the Actions menu for the job that you want to abort, select Abort.