In the Modify Case Step Dialog, click Lookup Variable and follow the instructions

14-16 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

4. Click Next.

5. In the Step Name field, enter a name for the Exception step.

6. Click Finish.

7. The Exception step is added in the steps hierarchy. You can now define the exception flow by adding new steps and organizing the hierarchy under this exception step.

14.2.4.2 Using Exception Handling

Defining exception handling for a Load Plan step consists of associating an Exception Step to this Load Plan step and defining the exception behavior. Exceptions steps can be set for each step except for When and Else steps. To define exception handling for a Load Plan step:

1. Open the Load Plan Editor and go to the Steps tab.

2. In the Steps Hierarchy table, select the step for which you want to define an

exception behavior. The Property Inspector displays the Step properties.

3. In the Exception Handling section of the Property Inspector, set the parameters as

follows: ■ Timeout s : Enter the maximum time in seconds that this step takes before it is aborted by the Load Plan. When a time-out is reached, the step is marked in error and the Exception step if defined is executed. In this case, the exception step never times out. If needed, a timeout can be set on a parent step to safe guard such a potential long running situation. If the step fails before the timeout and an exception step is executed, then the execution time of the step plus the execution time of the exception step should not exceed the timeout, otherwise the exception step will fail when the timeout is reached. Note that the default value of zero 0 indicates an infinite timeout. ■ Exception Step : From the list, select the Exception step to execute if this step fails. Note that only Exception steps that have been created and defined on the Exceptions tab of the Load Plan Editor appear in this list. See Section 14.2.4.1, Defining Exceptions Flows for more information on how to create an Exception step. ■ Exception Behavior : Defines how this step behaves in case an exception is encountered. Select one of the following: – Run Exception and Raise : Runs the Exception Step if any and raises the exception to the parent step. – Run Exception and Ignore : Runs the Exception Step if any and ignores the exception. The parent step is notified of a successful run. Note that if an exception is caused by the exception step itself, the parent step is notified of the failure. For Parallel steps only, the following parameters may be set: Max Error Child Count : Displays the maximum number of child steps in error that is accepted before this step is to be considered in error. When the number of failed child steps exceeds this value, the parallel step is considered failed. The currently running child steps are continued or stopped depending on the Restart Type parameter for this parallel step: Working with Load Plans 14-17 – If the Restart type is Restart from failed children, the Load Plan waits for all child sessions these are the currently running sessions and the ones waiting to be executed to run and complete before it raises the error to the parent step. – If the Restart Type is Restart all children, the Load Plan kills all running child sessions and does not start any new ones before it raises the error to the parent.

14.2.4.3 Defining the Restart Behavior

The Restart Type option defines how a step in error restarts when the Load Plan is restarted. You can define the Restart Type parameter in the Exception Handling section of the Properties Inspector. Depending on the step type, the Restart Type parameter can take the values listed in Table 14–5 .

14.3 Running Load Plans

You can run a Load Plan from Designer Navigator or Operator Navigator in ODI Studio. To run a Load Plan in Designer Navigator or Operator Navigator: 1. In the Load Plans and Scenarios accordion, select the Load Plan you want to execute.

2. Right-click and select Execute.

3. In the Start Load Plan dialog, select the execution parameters: Table 14–5 Restart Type Values Step Type Values and Description Serial ■ Restart all children : When the Load Plan is restarted and if this step is in error, the sequence of steps restarts from the first one. ■ Restart from failure : When the Load Plan is restarted and if this step is in error, the sequence of child steps starts from the one that has failed. Parallel ■ Restart all children : When the Load Plan is restarted and if this step is in error, all the child steps are restarted regardless of their status. This is the default value. ■ Restart from failed children : When the Load Plan is restarted and if this step is in error, only the failed child steps are restarted in parallel. Run Scenario ■ Restart from new session : When restarting the Load Plan and this Run Scenario step is in error, start the scenario and create a new session. This is the default value. ■ Restart from failed step : When restarting the Load Plan and this Run Scenario step is in error, restart the session from the step in error. All the tasks under this step are restarted. ■ Restart from failed task : When restarting the Load Plan and this Run Scenario step is in error, restart the session from the task in error. The same limitation as those described in Section 20.4, Restarting a Session apply to the sessions restarted from a failed step or failed task.