Resuming an application ingestion and replication job
You can resume an application ingestion and replication job that is in the Stopped, Aborted, or Failed status.
You can resume 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 resume an initial load job that has multiple subtasks, Application Ingestion and Replication starts only the subtasks that are in the Failed, Stopped, Aborted, or Queued status.
When you resume an incremental load job or a combined initial and incremental load job, Application Ingestion and Replication resumes replicating source data change from the last position recorded in the checkpoint file or target recovery table. A checkpoint will not be available unless a change record was processed for at least one of the tables during the first job run after deployment. If a checkpoint is not available, the job resumes processing from the configured restart point, which is the latest available position in the change stream by default.
When you resume an incremental load job, Application Ingestion and Replication resumes propagating source data from where it last left off.
1Navigate to the row for the job that you want to resume 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 the Monitor service
- All Jobs tab on the Data Ingestion and Replication page in Operational Insights
2In the Actions menu for the row, click Resume.
Note: The Resume command is not available if the job is in the Failed state because the task deployment failed.
A subtask is started for each source table.
If an error occurs, an error message is displayed at the top of the page.
You can also use the Resume icon beside the Actions menu to resume the job.
Restart and recovery for incremental load jobs
Application Ingestion and Replication can restart the incremental load jobs that stopped because of an error and the jobs that were stopped or aborted by users without any loss of change data.
After the first job run, Application Ingestion and Replication continually records an identifier for the processing position in the change stream as changes are applied to the target. The identifier is stored in a recovery table named INFORMATICA_CDC_RECOVERY on the target.
When you resume an incremental load job, the job uses the last position recorded in the recovery table to identify the change records that it must load to the target. This process ensures that all changes are ingested to the target.