Load Plans can be created from
the Designer or Operator Navigator.
To create a new Load Plan:
To create a new Load Plan:
1.
In
Designer Navigator or Operator Navigator, click New Load Plan
in the toolbar of the Load Plans and Scenarios accordion. The Load Plan Editor
is displayed.
2.
In
the Load Plan Editor, type in the Name, Folder Name, and a Description for
this Load Plan.
3.
Optionally,
set the following parameters:
Ø Log Sessions: Select how the session logs should be preserved for the
sessions started by the Load Plan. Possible values are:
v Always: Always keep session logs (Default)
v Never: Never keep session logs. Note that for Run Scenario steps
that are configured as Restart from Failed Step or Restart from Failed Task, the agent will behave as if the
parameter is set to Error as the whole session needs to
be preserved for restartability.
v Error: Only keep the session log if the session completed in an
error state.
Ø Log Session Step: Select how the
logs should be maintained for the session steps of each of the session started
by the Load Plan. Note that this applies only when the session log is
preserved. Possible values are:
v By Scenario Settings: Session step logs are preserved depending
on the scenario settings. Note that for scenarios created from packages, you
can specify whether to preserve or not the steps in the advanced step property
called Log Steps in the Journal. Other scenarios
preserve all the steps (Default).
v Never: Never keep session step logs. Note that for Run Scenario
steps that are configured as Restart from Failed Step
or Restart from Failed Task, the agent will behave as
if the parameter is set to Error as the whole session
needs to be preserved for restartability.
v Errors: Only keep session step log if the step is in an error state.
Ø Session Tasks Log Level: Select the log level for sessions. This
value corresponds to the Log Level value when starting
unitary scenarios. Default is 5. Note that when Run Scenario steps are
configured as Restart from Failed Step or Restart From Failed Task, this parameter is ignored as the
whole session needs to be preserved for restartability.
Ø Keywords: Enter a comma separated list of keywords that will be set on
the sessions started from this load plan. These keywords improve the
organization of ODI logs by session folders and automatic classification. Note
that you can overwrite these keywords at the level of the child steps.
4.
Optionally,
modify the Concurrent Execution Controller options:
Ø Enable the Limit
Concurrent Executions check box if you do not want to allow multiple
instances of this load plan to be run at the same time. If Limit
Concurrent Executions is disabled (unchecked), no restriction is imposed
and more than one instance of this load plan can be running simultaneously.
Ø If Limit Concurrent
Executions is enabled, set your desired Violation
Behavior:
v Raise Execution Error: if an instance of the load plan is
already running, attempting to run another instance will result in a session
being created but immediately ending with an execution error message
identifying the session that is currently running which caused the Concurrent
Execution Control error.
v Wait to Execute: if an instance of the load plan is
already running, additional executions will be placed in a wait status and the
system will poll for its turn to run. The session's status is updated
periodically to show the currently running session, as well as all concurrent
sessions (if any) that are waiting in line to run after the running instance is
complete.
If
you select this option, the Wait Polling Interval sets
how often the system will check to see if the running instance has completed.
You can only enter a Wait Polling Interval if Wait to Execute is selected.
If
you do not specify a wait polling interval, the default for the executing agent
will be used: in ODI 12.1.3, the default agent value is 30 seconds.
5.
Select
the Steps tab and add steps as described in Defining
the Load Plan Step Sequence.
6.
If
your Load Plan requires conditional branching, or if your scenarios use
variables, select the Variables tab and declare
variables as described in Declaring Load Plan Variables.
7.
To
add exception steps that are used in the event of a load plan step failing,
select the Exceptions tab and define exception steps as
described in Defining Exceptions Flows.
8.
From
the File menu, click Save.
The Load Plan appears in the
Load Plans and Scenarios accordion. You can organize your Load Plans by
grouping related Load Plans and Scenarios into a Load Plan and Scenarios
folder.