Troubleshooting DAC : Restarting an Execution Plan When the DAC Server Fails

If the DAC Server crashes while an execution plan is running, some workflows associated with the execution plan may have been submitted to Informatica. 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. You do not have to perform any manual intervention.
 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.

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.

Troubleshooting DAC : Recovering From a Lost Encryption Key

Recovering From a Lost Encryption Key

1.      The process of recovering from the loss of an encryption key involves clearing the encrypted data from the DAC repository, creating a new cwallet.sso file (with a new encryption key), and stamping the DAC repository with the new encryption key.

2.      This procedure involves steps that use automation utility commands.

3.      Before you can use these commands, you need to configure the automation utility property file.

To recover from the loss of an encryption key:

1. Remove all the encrypted data from the DAC repository by calling the automation utility command clearEncryptedData.
2. Call one of the following automation utility commands to generate a new cwallet.sso file:
• dbCredentials <cwallet.sso file path> <user name> -withKey

Use this command to generate a cwallet.sso file with a encryption key that you specify.

• dbCredentials <cwallet.sso file path> <user name> -randomKey

Use this command to generate a cwallet.sso file with a randomly generated encryption key.

3. Copy the new cwallet.sso file to the appropriate directory where the DAC repository can access it. The default directory is <DAC_Config_Location>\conf-shared\security\repository.
4. Stamp the DAC repository with the new encryption key:

1. Log in to the DAC Client.

The following message will be displayed:

Encryption key validation value is missing from the DAC repository. Would like to add it now?

2. Click OK to add the new encryption key to the DAC repository.
3. Enter the table owner name and password, and click OK.

A message informs you whether the operation was successful.

4. Distribute the new cwallet.sso file to all DAC installations that connect to this repository.

Troubleshooting DAC

1. Recovering From a Lost Encryption Key
2. Restarting an Execution Plan When the DAC Server Fails
3. Discarding a Failed Execution Plan
4. Failure of Aggregator Transformation Tasks with Sorted Input
5. In Case of Abnormal Termination of the DAC Server
6. DAC Task Failing on Non-English Operating System
7. DAC Task Failing in a Multi-Source Environment
8. Restoring the DAC Repository on Unicode Oracle Databases
9. Handling Parameter Files with Multi-Line Parameters
10. Resetting Refresh Dates at the Task Level
11. Error When Using Oracle(OCI8) Connection Type
12. Tables Are Not Truncated When More Than One Task Writes to the Same Target Table
13. Discrepancy Between DAC Task and Informatica Workflow
14. Making the DAC Server Visible to All Clients