Table of Contents

Search

  1. Preface
  2. Database Ingestion and Replication

Database Ingestion and Replication

Database Ingestion and Replication

Resuming a database ingestion and replication job

Resuming a
database ingestion and replication
job

You can resume a
database ingestion and replication
job that is in the Stopped, Aborted, or Failed state.
When you resume an initial load job that has multiple subtasks,
Database Ingestion and Replication
starts only the subtasks that are in a Failed, Stopped, Aborted, or Queued state.
When you resume an incremental load job or a combined initial and incremental load job,
Database 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.
For initial load jobs, the
Run
command might also be available. Click
Run
if you want the
database ingestion and replication
job to truncate all of the target tables and then reload the source data to the target tables.
  1. Navigate 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
  2. In the
    Actions
    menu for the row, click
    Resume
    .
    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.

0 COMMENTS

We’d like to hear from you!