ODI12c Load Plans in Production FAQS

1. What are the main tasks when using Load Plans in production?

·        Starting, monitoring, stopping, and restarting Load Plans

·        Scheduling Load Plans

·        Moving Load Plans across environments (Exporting, Importing, Versioning)

2. How can Load Plans be executed interactively in production?

You can:

·        Execute a Load Plan → Run it immediately

·        Restart a Load Plan Run → Resume failed steps according to Restart Type

·        Stop a Load Plan Run → Abort the execution

3. How are Load Plans scheduled?

·        Use ODI’s built-in scheduler or an external scheduler

·        Schedule can include scenarios or Load Plans

·        Allows automated execution at defined times

4. How are Load Plans moved across environments?

·        Through Exporting and Importing between repositories

·        Load Plans can be exported from development and imported into production

5. How do you export a Load Plan?

·        Can export a single Load Plan or multiple Load Plans at once

·        Child objects (steps, schedules, variables) can be included

·        Scenarios referenced by the Load Plan are NOT exported and must be exported separately

6. How do you import a Load Plan?

·        In development repository → Use Designer or Operator Navigator

·        In execution repository → Use Operator Navigator only

·        Referenced scenarios must be imported separately

7. How is versioning handled for Load Plans?

·        Load Plans can be deployed and promoted using versions and solutions

·        Supports production promotion and version control

8. Why export/import scenarios separately from Load Plans?

·        Load Plans reference scenarios but do not contain them

·        Ensures independent management and versioning of scenarios

9. What is the benefit of scheduling Load Plans?

·        Enables automated, repeatable execution

·        Reduces manual intervention in production runs

·        Supports timely execution of ETL processes

10. Why is versioning important for Load Plans?

·        Tracks changes and updates

·        Facilitates promotion from development to production

·        Maintains consistency across environments

ODI12c Handling Load Plan Exceptions and Restartability FAQS

1. What are the two features for handling errors in Load Plans?

Load Plans provide:

·        Exceptions → Define custom error handling flows

·        Restartability → Control how failed steps are restarted

2. What is an Exception Step?

·        A hierarchy of steps defined in the Exceptions tab of the Load Plan Editor

·        Automatically executed when an associated Load Plan step fails

·        Can optionally raise the exception to the parent step, triggering its exception flow

3. How is an Exception Step different from regular steps?

·        No root step for hierarchy — each exception step is a separate root

·        Serial, Parallel, Run Scenario, and Case steps in exceptions do not have exception properties

·        Exception steps themselves cannot raise another exception

4. How do you create an Exception Step?

·        Go to Exceptions tab → Add Step > Add Step Wizard

·        Select Exception as the step type

·        Enter a Step Name

·        Click Finish

·        Add child steps to define the exception flow

5. How do you associate an Exception Step to a Load Plan step?

·        Open Steps tab → select step → Property Inspector → Exception Handling

·        Set:

o   Timeout (s) → Maximum execution time before the step is aborted

o   Exception Step → The Exception Step to execute on failure

o   Exception Behavior → Either:

§  Run Exception and Raise → Executes Exception Step and raises to parent

§  Run Exception and Ignore → Executes Exception Step and ignores failure

6. What additional parameters exist for Parallel steps?

·        Max Error Child Count → Maximum failed child steps allowed before the parallel step fails

·        Behavior depends on Restart Type:

o   Restart from failed children → Waits for all child steps to complete before raising error

o   Restart all children → Kills running child steps and restarts none before raising error

7. What is Restartability in Load Plans?

Restartability defines how failed steps are resumed when a Load Plan is restarted, controlled by the Restart Type parameter.

8. What are Restart Type options for different step types?

Serial Steps:

·        Restart all children → Sequence restarts from the first step

·        Restart from failure → Sequence starts from the failed step

Parallel Steps:

·        Restart all children → All child steps are restarted (default)

·        Restart from failed children → Only failed child steps are restarted

Run Scenario Steps:

·        Restart from new session → Start scenario with a new session (default)

·        Restart from failed step → Restart scenario from failed step

·        Restart from failed task → Restart scenario from failed task

9. Why is exception handling important in Load Plans?

·        Provides controlled recovery from failures

·        Ensures business rules and error flows are executed

·        Prevents unexpected failures from cascading

10. Why is restartability important?

·        Minimizes re-execution of successfully completed steps

·        Supports parallel step recovery

·        Ensures Load Plan consistency after failures