Stopping an application ingestion and replication job
You can stop an application ingestion and replication job of any load type that is in the Up and Running, Running with Warning, or On Hold status.
When you stop 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.
Note: Before stopping an application ingestion and replication incremental load or combined load job that has a Snowflake target and uses the Superpipe option, ensure that all ingested data in the change stream has been merged into the target. Otherwise, if the job is not restarted for an extended period or before the stream expires, any data that remains in the stream is lost and can’t be recovered.
For initial load jobs, the job stops only after its subtasks that are already running complete their operation. The subtasks that are not running remain in their current states.
1Navigate to the row for the job that you want to stop in any of the following monitoring interfaces:
- My Jobs page that's accessed from the navigation bar of the Home page
- All Jobs page in Monitor
- All Jobs tab on the Data Ingestion and Replication page in Operational Insights
You can also use the Stop icon beside the Actions menu to stop the job.
2From the Actions menu for the job, select Stop.
The job state switches to Stopping and then to Stopped.
Tip: If the Stop operation is taking too long, you can abort the job.