Undeploying a database ingestion and replication job
You can undeploy a database ingestion and replication job that has a status of Aborted, Completed, Deployed, Failed, or Stopped. You might want to undeploy a job if you no longer need to run the job or you need to change a connection or property in the associated task that cannot be edited without first undeploying the job.
Before you attempt to undeploy a job, ensure that it is not running.
After the job is undeployed, you cannot run it again or redeploy it. If you want to run a job for the associated database ingestion and replication task again, you must deploy the task again from the task wizard to create a new job instance. For example, if you want to change the target connection, undeploy the job, edit the task to change the connection, deploy the task again, and then run the new job instance.
1Navigate to the row for the job that you want to undeploy in any of the following monitoring interfaces:
- My Jobs page that's accessed from the navigation bar of the Home page
- All Jobs and Running Jobs pages 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 Undeploy.
If the undeploy operation fails, the job status switches to Failed, even if it was in the Aborted state, or remains as Failed.
Note: After undeploying jobs, do not immediately shut down the Secure Agent. Database Ingestion and Replication requires some time to clean up files for tasks in the /root/infaagent/apps/Database_Ingestion/data/tasks directory.