Running a deployed database ingestion and replication job
You can run a database ingestion and replication job that has been previously deployed and is in a state other than Undeployed.
After you deploy a task successfully in the task wizard, the associated job instance is in the Deployed state. You can run it directly from the task wizard using the Run option in the Actions menu.
You can also run the job from any of the following monitoring interfaces: the My Jobs page that's accessed from the navigation bar of the Home page, the All Jobs page in Monitor, or the All Jobs tab on the Data Ingestion and Replication page in Operational Insights .
1In any of the monitoring interfaces, navigate to the row for the job that you want to run.
2In the Actions menu for the row, click Run.
A subtask is started for each source table.
Note:
- If the initial load portion of a combined initial and incremental load job fails to load data from a source table to a target table, the database ingestion and replication job retries the subtask for the table up to three times. The interval between retries is a minimum of 60 seconds. If all of the initial load retries fail, the subtask acquires the state of Error and the table is excluded from replication. The job then tries to proceed with incremental loading. In this case, the job status changes to Running with Warning.
- If an initial load job detects inconsistencies between column definitions in the source and target tables, the job drops the target table and then re-creates it to be consistent with the source table, prior to loading source data to the target.
- For initial load and combined tasks, the initial load might take a long time to perform if the source tables contain many rows.