task and save it, deploy the task to create an executable job instance on the on-premises system that contains the Secure Agent and the Database Ingestion agent service and DBMI packages. You must deploy the task before you can run the job. The deploy process also validates the task definition.
Before you deploy a task that has a Microsoft Azure Synapse Analytics or Snowflake target, drop any existing target tables that do not match the structure of the source tables, for example, because of added or dropped source columns or altered column null constraints or data types. When you deploy the task, the target tables are generated based the latest source structure.
To deploy a task, in the
database ingestion
task wizard, save the completed task definition and then click
Deploy
.
After you deploy a task successfully, the associated job instance is in the Deployed state. You can run it from the
My Jobs
page in Mass Ingestion or from the
All Jobs
tab on the
Mass Ingestion
page in
Operational Insights
or
Monitor
.
Deployment considerations:
If you included spaces in the database ingestion task name, the spaces are omitted from the corresponding job name for the generated job instance.
If the deployment process fails, the job status switches to Failed. To diagnose the error, download the error log from the
My Jobs
page in Mass Ingestion or the
All Jobs
tab on the
Mass Ingestion
page in
Operational Insights
or
Monitor
. In the Actions menu for the job, click
Error Log
. After you resolve the problem, deploy the task again either from the
database ingestion
task wizard or from the Actions menu for the failed job.
If you undeploy a job and then want to run a job for the associated ingestion task again, you must deploy the task again to create a new job instance. The new job instance name ends with an incremented number in the format
taskname
-
job_instance_number
. The job instance number is incremented each time you deploy the ingestion task by adding 1 to the maximum instance number across all ingestion jobs.
If the Secure Agent is restarted while the task is deploying, the job status switches to Failed. Avoid restarting the Secure Agent while tasks are being deployed.
If a task appears to be hung in the Deploying state, restart the Secure Agent. The associated job instance acquires the status of Failed. You can then deploy it again.
ASK INFAPreview
