The DAC console controls ETL. It runs an Execution Plan for the ETL, which contains Tasks.
Excerpts of information recorded in the DAC logs are displayed in the DAC console > Current Run > Tasks and Task Details Tabs. This means that you can choose to use the DAC Execution Views to drill down on unexpected behavior, or you can use the DAC logs.
A typical ETL investigation process would be:
1) Start off with default logging levels, to avoid system resource overload
2) Review the DAC Execution > Current Run > Tasks and Tasks Details
3) Review the Tasks, filtered by ‘Failed Tasks’ (colored pink)
4) Note the Task Name, Execution Type, and Task Phase
5) Review the Task Details, filtered by ‘Failed’ Tasks.
6) Sort the Failed tasks to find the one that failed first.
• Note the ‘Task Name’ (same as above), ‘Name’ (=Informatica workflow name), and ‘End Timestamp’. Double click on the ‘Status Description’ column, which will in give you further information, in context of the type of task which failed. For example if an Informatica session was being executed (Task Execution Type= Informatica), and has failed, it will give the session name, on the other hand, if the DAC task that failed was “internal”, it will not be relevant to give an Informatica session name.
Note: Alternatively you could use the DAC logs, starting with the etl_summary, to obtain similar info.
By doing above analysis now we have:-
• Obtained an overview of the ETL execution
• Found out which Informatica workflow and sessions (and their logs) to use if we need to find more detailed info.
Now we can use Informatica logs to:
• Find detailed information about Informatica Tasks – Workflows and Sessions
For more information on logs please refer to my post.