Execution Plans


Types of Execution Plans

An execution plan is a unit of work that enables you to organize, schedule, and
execute ETL processes.

An execution plan comprises the following objects:

subject areas,
ordered tasks,
 indexes,
tags,
parameters,
source system folders,
phases.

DAC supports single-source and multi-source execution plans, which are described in the following sections:

About Single-Source Execution Plans
About Multi-Source Execution Plans

About Single-Source Execution Plans

A single-source execution plan extracts data from a single instance of a single source system container, such as Siebel 7.8 or Oracle EBS 11.
For information about data extraction and loads for single-source execution plans, see "Common Extract and Load Scenarios".

About Multi-Source Execution Plans

There are two types of multi-source execution plans:

Homogeneous

Types of Execution Plans 9-2 Oracle Business Intelligence Data Warehouse Administration Console User’s Guide
This type of execution plan extracts data from multiple instances of the same
source system.
 For example, a business might have an instance of Oracle EBS 11i in one location and time zone and another instance of Oracle EBS 11i in another location and time zone.
 In such cases, the timing of data extraction from the different instances can be staggered to meet your business requirements.



 Heterogeneous

This type of execution plan extracts data from one or more instances of dissimilar source systems.
 For example, a business might have an instance of Siebel 7.8 in one location, an instance of Oracle EBS 11i in another location, and a second instance of Oracle EBS 11i in yet a third location.
 You can also stagger the timing of data extraction when you use this type of execution plan.
For information about data extraction and loads for multi-source execution plans, see "Common Extract and Load Scenarios".

Multi-Source Order of Execution

The order in which DAC loads data from the different sources that are participating in the ETL process is determined by the priority of the physical data source connection (set in the Physical Data Sources tab of the Setup view).-
 The Priority property ensures that tasks attempting to write to the same target table will not be in conflict.

Delay

As shown in Figure 9–1, the Delay property is located in the Parameters subtab in the Execution Plans tab of the Execute view.
You set this property to specify how many minutes an extract of a data source will be delayed after the first extract of a multiple source extract process started.

Figure 9–1 Multi-Source Delay Property

Folder Level Priorities
As shown in Figure 9–2, you need to set the folder level priority in the Task Physical Folders dialog box, which you by selecting Tools, then Seed Data, and then Task Physical Folders.
Common Extract and Load Scenarios Building,


No comments:

Post a Comment

Popular Posts