Dac(obiee) 3h3d6a

DAC (OBIEE) DAC stands for Data Warehouse Application Console. It is an essential component of Oracle BI application architecture. DAC serves the following purposes: 1. •DAC is a metadata driven istration and deployment tool for ETL and data warehouse objects 2. Used by warehouse developers and ETL 3. Application Configuration • Manages metadata-driven task dependencies and relationships • Allows creating custom ETL execution plans • Allows for dry-run development and testing 4. Execution • Enables parallel loading for high performance ETL • Facilitates in index management and database statistics collection • Automates change capture for Siebel OLTP • Assists in capturing deleted records • Fine grain restartability 5. Monitoring • Enables remote and monitoring • Provides runtime metadata validation checks • Provides in-context documentation

Execution Plan (DAC, OBIA, OBIEE) An execution plan includes the ordered tasks to be executed together in order to populated one ore more subject area. An execution plan is generated by DAC based the logical dependencies among the tables and tasks required for populating the tables involved in a subject area. You run the ETL jobs for Oracle BI Apps from DAC by running the execution plan. You can schedule the execution to run periodically in the DAC. You can also monitor execution plan process in the DAC. An execution plan is the unit of work for you to organize, schedule, execute, and monitor your ETL processes.

Why do I need to use DAC from Oracle BI EE? Data Warehouse Application Console (DAC) works together with Informatica to accomplish the ETL for pre-packaged BI applications. Here is what happens behind the scene: • DAC publish the changes from OLTP • Informatica extracts the changes from the change log published by DAC as well as from the base table • Informatica load the data to the stage tables and the target tables in the data warehouse • DAC manage the performance by dropping indexes, truncating stage tables, rebuilding the indexes, and analyzing the tables during the process If you do not use DAC, you have to write your own custom change capture process and need to redesign from scratch an ETL method that allow the restart of the ETL process from point of failure at record level. The biggest saving is that DAC can survive during the upgrade, while your custom processes cannot.