Executing a Load Plan from ODI Studio

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

2. Select New Scheduling. The Scheduling editor is displayed.

3. On the Definition tab of the Scheduling editor specify the parameters as follows:

The Status parameters define the activation of the schedule. The Execution parameters define the frequency of execution for each execution cycle.

4. On the Execution Cycle tab, specify the parameters for the repeat mode of the

scenario as follows:

5. On the Variables tab, unselect Latest Value for variables for which you want to

provide a Value. Only variables used in the scenario or Load Plan and flagged as parameters for this scenario or Load Plan appear in this tab. Properties Description Context Context into which the scenario or Load Plan is started. Agent Agent executing the scenario or Load Plan. Log Level Level of logging information to retain. Properties Description Active The scheduling will be active when the agent is restarted or when the scheduling of the physical agent is updated. Inactive The schedule is not active and will not run. Active for the period Activity range of the schedule. A schedule active for a period of time will only run within this given period. Properties Description Execution Frequency of execution option annual, monthly,... simple. This option is completed by a set of options that depend on this main option. Properties Description None Execute once The scenario or Load Plan is executed only one time. Many times The scenario or Load Plan is repeated several times. ■ Maximum number of repetitions : The maximum number of times the scenario is repeated during the cycle. ■ Maximum Cycle Duration: As soon as the maximum time is reached, the scenario is no longer restarted, and the cycle stops. ■ Interval between repetitions: The downtime between each scenario execution. Constraints Allows limitations to be placed on one cycle iteration, in the event of a problem during execution. ■ Number of Attempts on Failure : Maximum number of consecutive execution attempts for one iteration. ■ Stop Execution After : Maximum execution time for one iteration. If this time is reached, the scenario or Load Plan is automatically stopped.