Creating a New Load Plan

Steps to Create a New Load Plan

1. Access the Load Plan Editor:
• In either Designer Navigator or Operator Navigator, click on New Load Plan in the toolbar under the Load Plans and Scenarios accordion.
• This will open the Load Plan Editor.
2. Enter Basic Information:
• Name: Provide a name for the Load Plan.
• Folder Name: Specify the folder where the Load Plan will be stored.
• Description: Enter a description of the Load Plan.
3. Set Optional Parameters (Optional Step):
• You may configure additional parameters, as needed (though this is optional).

Steps for Configuring Log Sessions in a Load Plan

1.     Access the Log Sessions Setting:

• In the Load Plan Editor, locate the Log Sessions setting, which controls how session logs should be preserved for sessions started by the Load Plan.

2.     Choose a Log Session Preservation Option:

• Always: Select this option to always keep the session logs. This is the default setting.
• Never: Choose this option if you do not want to keep any session logs. Note that for Run Scenario steps configured as Restart from Failed Step or Restart from Failed Task, the agent will behave as if the parameter is set to Error, since the entire session needs to be preserved for restartability.
• Error: Select this option to only keep the session logs if the session completes with an error state.

3.     Save Your Settings:

• After selecting your preferred log session option, save the configuration to apply the changes to the Load Plan.

Steps for Configuring Log Session Step in a Load Plan

1.     Access the Log Session Step Setting:

• In the Load Plan Editor, locate the Log Session Step setting, which determines how session step logs should be maintained for each session started by the Load Plan.

2.     Choose a Log Session Step Preservation Option:

• By Scenario Settings: Choose this option to preserve session step logs based on the scenario settings. For scenarios created from packages, you can define whether to preserve step logs using the Log Steps in the Journal property. Other scenarios will preserve all steps by default.
• Never: Select this option if you do not want to preserve any session step logs. For Run Scenario steps configured as Restart from Failed Step or Restart from Failed Task, the agent will behave as if the parameter is set to Errors, since the entire session needs to be preserved for restartability.
• Errors: Choose this option to preserve session step logs only if the step results in an error state.

3.     Save Your Settings:

• After selecting your preferred option for Log Session Step, save the configuration to apply the changes to the Load Plan.

Let me know if you need further clarification!

Steps for Configuring Session Tasks Log Level and Keywords in a Load Plan

1.     Access the Session Tasks Log Level Setting:

• In the Load Plan Editor, locate the Session Tasks Log Level setting, which controls the log level for sessions started by the Load Plan.

2.     Set the Log Level for Sessions:

• Select the Log Level: Choose the desired log level for the sessions. This log level corresponds to the Log Level value when starting unitary scenarios. The default log level is 5.
• Note: If the Run Scenario steps are configured as Restart from Failed Step or Restart from Failed Task, this log level setting is ignored, as the whole session must be preserved for restartability.

3.     Enter Keywords for Session Organization:

• Enter Keywords: Provide a comma-separated list of keywords that will be applied to the sessions started by this Load Plan.
• Purpose: These keywords help improve the organization of ODI logs by session folders and enable automatic classification.
• Note: You can overwrite these keywords at the child step level.

4.     Save Your Settings:

• After configuring the Session Tasks Log Level and Keywords, save the changes to apply them to the Load Plan.

Let me know if you need more details or clarification!

Steps to Modify Concurrent Execution Controller Options and Complete the Load Plan Configuration

1.     Access Concurrent Execution Controller Options:

• In the Load Plan Editor, find the Concurrent Execution Controller section.

2.     Enable the "Limit Concurrent Executions" Option (Optional):

• Check the "Limit Concurrent Executions" box if you do not want to allow multiple instances of the Load Plan to run simultaneously.
• If unchecked, no restriction is applied, and multiple instances can run at the same time.

3.     Set Violation Behavior (If "Limit Concurrent Executions" is Enabled):

• Raise Execution Error: Select this option to create a session that immediately ends with an execution error message when another instance is already running. The message will indicate which session is causing the conflict.
• Wait to Execute: Choose this option if you want additional executions to wait until the current instance completes. The system will place waiting sessions in a queue, updating their status periodically, and showing all waiting sessions.
• If Wait to Execute is selected, set the Wait Polling Interval to define how often the system checks for completion. (Note: The default interval for ODI 12.1.3 is 30 seconds, unless specified otherwise.)

4.     Add Steps to the Load Plan:

• Navigate to the Steps tab and add steps according to the instructions in Defining the Load Plan Step Sequence.

5.     Declare Variables (If Needed):

• If your Load Plan requires conditional branching or uses variables, go to the Variables tab and declare necessary variables as outlined in Declaring Load Plan Variables.

6.     Define Exception Steps (If Needed):

• If you need exception handling for failed steps, select the Exceptions tab and define exception steps as explained in Defining Exception Flows.

7.     Save the Load Plan:

• From the File menu, click Save to save the Load Plan.

8.     Organize the Load Plan:

• The Load Plan will appear in the Load Plans and Scenarios accordion. You can organize it by grouping related Load Plans and Scenarios into a Load Plan and Scenarios folder.