Troubleshooting DAC : Restarting an Execution Plan That Failed

1.      If the DAC Server crashes while an execution plan is running, some workflows associated with the execution plan may have been submitted to Informatica.

2.      When the DAC Server is restarted and the failed ETL process resumes, the workflows that DAC submitted to Informatica before the crash may have completed or failed or may still be running.

3.      You do not have to perform any manual intervention.

4.      DAC manages the tasks submitted for execution prior to the crash in the following manner:

• Running. If a workflow is still running in Informatica, DAC waits for the running workflow to finish execution.
• If the workflow has successfully completed, DAC will change the status of the task detail to Completed and will resume execution of the successors.
• If the workflow has failed, DAC will change the status of the task detail to Failed and will eventually halt the ETL. This is analogous to a normal failure encountered during ETL execution.
• Completed. If the workflow had completed in Informatica, the task will not be re-run. DAC will change the status of the task detail to Completed and will resume execution of the successors.
• Failed. If the workflow in Informatica had failed, DAC will resubmit the workflow for execution when the ETL process restarts.

Note: If a failed task includes truncate statements, the truncate action will occur again when the task is restarted. This will also trigger the Upon Failure Restart action if one is defined for the task.