Managing Load Plans

The tasks for managing load plans are usually performed by either ETL developers or ETL operators. The tasks in this section are grouped by the role that generally performs the task, as listed below.

ETL Developer Tasks

1. Defining Load Plans
2. Copying Load Plans
3. Editing Load Plans
4. Generating Load Plans
5. Scheduling Load Plans
6. Executing Load Plans

ETL Operator Tasks

1. Monitoring Load Plan Runs
2. Restarting Load Plans
3. Stopping Load Plans

Overview of Load Plan Life Cycle

A load plan life cycle comprises the following phases:

• Phase 1: Define load plan

In this phase, you define load plan properties in the Oracle BI Applications Configuration Manager, including selecting a data source and one or more fact groups. This selection determines which steps need to be performed during the ETL process.

• Phase 2: Generate load plan

In this phase, you launch a generation process from Oracle BI Applications Configuration Manager that propagates the load plan properties to the ODI Repository, where the load plan is built.

• Phase 3: Execute load plan

In this phase, you start a load plan run from Oracle BI Applications Configuration Manager, which executes the steps of the load plan. Executing a load plan creates a load plan instance and a first load plan run. If a run is restarted a new load plan run is created under this load plan instance. Each execution attempt of the load plan instance is preserved as a different load plan run in the log.

• Phase 4: Monitor load plan

In this phase, you monitor the load plan run in the Load Plan Details page of the Oracle BI Applications Configuration Manager. The Load Plan Details page provides a view of the ODI Repository through Oracle Data Integrator Console.