OBIA - Data Warehouse Application Console (DAC)

About

DAC is a command and control interface for the OBIA data warehouse to allow for set up, configuration, administration, and monitoring of data warehouse processes.

Designed specifically for organizations using Oracle Business Intelligence Applications implementing Informatica PowerCenter as their ETL tool, Oracle DAC offers a rich suite of application-specific features that complement the Informatica ETL platform:

• Dynamic generation of subject areas and execution plans
• Dynamic settings for parallelism and load balancing
• Intelligent task queue engine based on user-defined and computed scores
• Index management for ETL and query performance
• Embedded high-performance OTLP change capture techniques
• Restart from any point of failure
• Phase-based analysis tools for isolating ETL bottlenecks

Other Oracle DAC features help you minimize installation, setup, and configuration time; manage metadata driven dependencies and relationships; and apply performance-based execution techniques.

Articles Related

• OBIA - DAC - Load Type
• DAC - Installation and Configuration v10.1.3.4.1 on Windows
• DAC - Installation on Unix
• DAC - User Account Management

Parameter

Some parameters are defined as Source System Parameters… Other are defined in the task (Design > Tasks > select and choose the Parameters tab below).

Why do I need to use DAC ?

Posted by Dylan Wan on January 8, 2007

Data Warehouse Application Console (DAC) works together with Informatica to acomplish the ETL for pre-packaged BI applications.

Here are what happen 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.