Creating a New Load Plan FAQS

1. What is a Load Plan?
• A Load Plan is a detailed plan for managing and organizing loads in a system, often used for logistics, transport, or operation scheduling.
2. Where can I create a Load Plan?
• You can create a Load Plan from either the Designer Navigator or the Operator Navigator.
3. How do I open the Load Plan Editor?
• In either Navigator, click on New Load Plan in the toolbar under the Load Plans and Scenarios accordion to open the Load Plan Editor.
4. What information is required to create a Load Plan?
• You must provide a Name, Folder Name, and Description for the Load Plan.
5. Can I set additional parameters when creating a Load Plan?
• Yes, there are optional parameters you can set, depending on your needs, to further define the load plan.
6. Can I modify an existing Load Plan?
• Yes, once a Load Plan is created, you can edit or update it from the Load Plan Editor.
7. Is the description of the Load Plan mandatory?
• No, the description is optional, but it is recommended to provide it for better clarity and understanding of the Load Plan’s purpose.
8. Can I organize Load Plans into folders?
• Yes, you can assign a Folder Name to organize and manage your Load Plans better.
9. What happens after I create a Load Plan?
• After creating the Load Plan, you can continue to configure it further or proceed with operational tasks such as assigning it to scenarios or executing it in the system.
10. Can multiple users create Load Plans?

• Yes, users with the appropriate permissions can create and manage Load Plans from either the Designer Navigator or the Operator Navigator.

Let me know if you need clarification or further questions!

Log Sessions in a Load Plan

1. What does the "Log Sessions" setting do in a Load Plan?
• The "Log Sessions" setting determines how session logs should be preserved for the sessions started by the Load Plan.
2. What are the available options for Log Sessions?
• Always: Session logs are always preserved (default setting).
• Never: Session logs are not saved. For certain steps like Restart from Failed Step/Task, the agent will behave as if set to Error.
• Error: Session logs are only saved if the session ends in an error state.
3. What is the default setting for Log Sessions?
• The default setting is Always, meaning session logs are always kept.
4. What happens if I choose "Never" for Log Sessions?
• If you choose Never, session logs will not be saved. However, for steps that involve restarting from a failed task or step, the session logs will still be preserved to ensure restartability.
5. Why would I select "Error" for Log Sessions?
• You may select Error if you only want to preserve logs when the session fails. This can help reduce storage usage by not keeping logs for successful sessions.
6. Can I change the Log Sessions setting after the Load Plan is created?
• Yes, you can update the Log Sessions setting at any time by editing the Load Plan in the Load Plan Editor.
7. How does selecting "Never" affect restartable tasks?
• If you select Never, for tasks configured to restart from a failed step or task, the system will still preserve session logs to maintain restartability.
8. What happens if I don't configure the Log Sessions setting?
• If the setting is not explicitly configured, it will default to Always, and session logs will be preserved for all sessions.

Let me know if you need more details on this!

Log Session Step in a Load Plan

1. What is the purpose of the "Log Session Step" setting in a Load Plan?
• The "Log Session Step" setting controls how session step logs are maintained for each session started by the Load Plan, but only if the session logs are preserved.
2. What are the available options for "Log Session Step"?
• By Scenario Settings: Session step logs are preserved according to the scenario settings. For scenarios created from packages, you can specify whether to preserve steps through the Log Steps in the Journal property. Other scenarios preserve all steps by default.
• Never: No session step logs will be preserved. For steps configured to restart from a failed step or task, the agent will preserve the entire session instead.
• Errors: Session step logs will only be kept if the step results in an error state.
3. What is the default setting for "Log Session Step"?
• The default setting is By Scenario Settings, which preserves session step logs based on the scenario configuration.
4. What happens if I choose "Never" for Log Session Step?
• If you choose Never, session step logs will not be preserved. However, for restartable tasks (like Restart from Failed Step or Restart from Failed Task), the agent will ensure that the entire session is preserved, even if the session step logs are not.
5. Why would I select "Errors" for Log Session Step?
• You might choose Errors if you only want to preserve session step logs when there is an error during the execution of a specific step, helping to reduce storage by not saving logs for successful steps.
6. Can I modify the "Log Session Step" setting after creating a Load Plan?
• Yes, you can change the Log Session Step setting anytime by editing the Load Plan in the Load Plan Editor.
7. How does selecting "By Scenario Settings" affect session step logs?
• If you select By Scenario Settings, session step logs will be preserved as defined in the scenario. If the scenario is created from a package, the preservation of logs can be configured via the Log Steps in the Journal property, while other scenarios will preserve all steps by default.
8. What happens if I do not configure the "Log Session Step" setting?
• If you do not configure this setting, it will default to By Scenario Settings, meaning session step logs will be preserved based on the scenario configuration.

Let me know if you need further details or clarification!

Session Tasks Log Level and Keywords in a Load Plan

1. What is the "Session Tasks Log Level" setting in a Load Plan?
• The Session Tasks Log Level controls the log level for sessions started by the Load Plan. This value corresponds to the log level when starting unitary scenarios, with the default set to 5.
2. What are the possible values for the Session Tasks Log Level?
• The value for the Session Tasks Log Level ranges from 1 to 5, where 5 is typically the default level. A higher number often corresponds to more detailed logging.
3. What happens if I choose a "Restart from Failed Step" or "Restart from Failed Task" in a Run Scenario step?
• If you configure Run Scenario steps as Restart from Failed Step or Restart from Failed Task, the Session Tasks Log Level setting will be ignored because the entire session must be preserved for restartability.
4. What is the purpose of entering keywords for sessions?
• Keywords help improve the organization of ODI logs by classifying sessions into specific folders, making it easier to manage and find relevant session logs.
5. How should I format the keywords for session classification?
• Keywords should be entered as a comma-separated list (e.g., keyword1, keyword2, keyword3). These keywords will be applied to the sessions started by the Load Plan.
6. Can I change the keywords for child steps in the Load Plan?
• Yes, you can overwrite the keywords at the level of the child steps to provide more specific classification for individual steps.
7. Can I modify the log level or keywords after creating the Load Plan?
• Yes, you can change both the Session Tasks Log Level and the Keywords anytime by editing the Load Plan in the Load Plan Editor.
8. What happens if I do not configure the Session Tasks Log Level or Keywords?
• If you do not configure them, the default Log Level 5 will be used, and no keywords will be applied unless specified elsewhere in the child steps.

Let me know if you have further questions!

Concurrent Execution Controller and Load Plan Configuration

1. What is the "Limit Concurrent Executions" option?
• The "Limit Concurrent Executions" option restricts whether multiple instances of the same Load Plan can run at the same time. If enabled, only one instance can run, and other instances will be handled according to the violation behavior settings.
2. What happens if I leave the "Limit Concurrent Executions" option disabled?
• If unchecked, no limit is applied, and multiple instances of the Load Plan can run simultaneously without any restriction.
3. What are the possible violation behaviors if "Limit Concurrent Executions" is enabled?
• Raise Execution Error: If a Load Plan instance is already running, any new attempt to execute the Load Plan will create a session that ends immediately with an error message identifying the currently running session.
• Wait to Execute: New instances will be placed in a waiting state and will be executed once the current instance completes. The system will periodically update the status of all waiting sessions and show their position in the queue.
4. How often does the system check if the current Load Plan instance has completed when using "Wait to Execute"?
• The system checks the completion status based on the Wait Polling Interval. If not specified, the default polling interval is 30 seconds for ODI 12.1.3.
5. Can I add steps to my Load Plan?
• Yes, you can add steps by going to the Steps tab in the Load Plan Editor. Follow the instructions in Defining the Load Plan Step Sequence to add and sequence steps.
6. How do I declare variables in the Load Plan?
• If your Load Plan uses variables or requires conditional branching, go to the Variables tab and declare the necessary variables as outlined in Declaring Load Plan Variables.
7. What are exception steps, and when should I define them?
• Exception steps are used to handle scenarios where a Load Plan step fails. You can define these steps in the Exceptions tab to ensure proper handling of errors, as explained in Defining Exception Flows.
8. How do I save my Load Plan after making changes?
• After configuring the Load Plan, save it by going to the File menu and selecting Save.
9. Can I organize my Load Plans in folders?
• Yes, you can group related Load Plans and Scenarios into a folder for better organization in the Load Plans and Scenarios accordion.
10. What happens if I don't set a "Wait Polling Interval"?
• If you choose Wait to Execute but don't specify a Wait Polling Interval, the default polling interval will be used (30 seconds in ODI 12.1.3).