Load Plan FAQS

1. What is a Load Plan in ODI 12c?

A Load Plan is an executable object in ODI that organizes the execution of scenarios, packages, mappings, variables, and procedures. It allows steps to be executed sequentially, in parallel, or conditionally, providing control over large-scale ETL operations.

2. Why are Load Plans used?

Load Plans are used to:

·        Organize execution of thousands of tables and hundreds of scenarios

·        Maximize data throughput within batch windows

·        Ensure efficient and reliable ETL processes for large data warehouses

3. What is the structure of a Load Plan?

·        A Load Plan contains a hierarchy of steps.

·        Leaf nodes are typically Scenarios.

·        Steps can include:

o   Packages

o   Mappings

o   Procedures

o   Variables

4. Can Load Plans handle variables?

Yes. Load Plans allow setting and using variables at multiple levels for dynamic execution and parameterization.

5. Do Load Plans support exception handling?

Yes. Load Plans support exception handling strategies in case a scenario or step ends in error. They also support restartability from the point of failure.

6. How can Load Plans be executed?

Load Plans can be executed from:

·        Command line

·        ODI Studio

·        ODI Console

·        Web Service interface
They can also be scheduled using the ODI Agent’s scheduler or an external scheduler.

7. What is a Load Plan Instance and Load Plan Run?

·        Load Plan Instance: Created each time a Load Plan is started.

·        Load Plan Run: Each attempt to execute a Load Plan Instance is considered a separate run.

8. Can Load Plans be modified in production?

Yes. In production:

·        Steps can be enabled or disabled

·        Load Plans can be modified according to operational needs

·        Some design operations may be limited depending on whether connected to a development or execution repository.

9. Where are Load Plans stored?

Load Plans are stored in the Work Repository. They can also be:

·        Exported and imported to another repository

·        Versioned for change tracking and deployment

10. Where can Load Plans be viewed?

·        Designer Navigator → For design and editing

·        Operator Navigator → For execution monitoring

o   Load Plans and Scenarios accordion: Shows all Load Plans

o   Load Plan Executions accordion: Shows all Load Plan Runs

11. Can Load Plans run in parallel?

Yes. Steps in a Load Plan can be executed in parallel, sequentially, or conditionally, depending on the design.

12. What is the benefit of using Load Plans over individual scenarios?

·        Better organization of large ETL workloads

·        Higher throughput for batch processing

·        Error handling and restartability capabilities

·        Flexible scheduling and execution control