Running Load Plans FAQS

1. What is a Load Plan in ODI Studio?

• A Load Plan is a set of ordered steps that automate the execution of integration processes in Oracle Data Integrator (ODI). It helps in orchestrating multiple ODI jobs, procedures, or scenarios in a specific sequence.

2. Can I run multiple instances of a Load Plan at the same time?

• By default, ODI allows multiple instances of a Load Plan to run concurrently. However, this could lead to simultaneous data read/write operations on the same data sources. To prevent this, use the Limit Concurrent Executions option to restrict concurrent execution.

3. Where can I run a Load Plan?

• You can run a Load Plan from either the Designer Navigator or the Operator Navigator within ODI Studio.

4. How do I execute a Load Plan?

• In Designer Navigator or Operator Navigator, select the Load Plan from the Load Plans and Scenarios section, right-click, and select Execute. Then, set the execution parameters (e.g., context, logical agent, variable values) in the dialog and click OK to start.

5. What are the execution parameters I need to configure?

• The parameters include:
• Context: The context in which the Load Plan will execute.
• Logical Agent: The agent responsible for running the Load Plan.
• Variables: Any startup values for the variables used in the Load Plan.

6. How can I monitor the progress of a Load Plan execution?

• Once the Load Plan starts, you can track its execution status in the Operator Navigator. You will also see the Load Plan Started dialog for confirmation.

7. How long is the execution log history retained for Load Plans?

• The default retention period for execution logs is 7 days. You can change this value by modifying the Keep Log History (days) parameter in the Load Plan settings if you need to retain the logs for a longer period.

8. What happens when the "Limit Concurrent Executions" option is not configured?

• If the Limit Concurrent Executions option is not set, multiple instances of the Load Plan may run at the same time, potentially leading to data conflicts when both instances interact with the same data sources or targets.

9. What is the purpose of purge jobs in ODI?

• Purge jobs automatically clean up the execution logs and history of Load Plans. These jobs are managed by the OracleDIAgent based on the Keep Log History (days) setting. Purge jobs are internal and do not appear in the Operator panel.

10. Can I customize the execution parameters for a Load Plan?

• Yes, you can configure the execution parameters such as context, logical agent, and variables according to your specific needs in the Start Load Plan dialog before initiating the execution.

11. What happens if a Load Plan fails during execution?

• If a Load Plan fails, you can review the execution details and error logs in the Operator Navigator to identify the issue and take corrective actions. Depending on the configuration, you may also receive notifications about the failure.

12. How can I set the Load Plan to run at a specific time?

• To schedule a Load Plan to run at a specific time, use the Scheduler functionality in ODI Studio. You can define the schedule along with execution parameters for automation.

13. What do I do if I need to stop a running Load Plan?

• If you need to stop a Load Plan while it's running, you can do so from the Operator Navigator by selecting the running Load Plan instance and choosing the option to stop or abort it.

14. Can I view historical data about previous executions of Load Plans?

• Yes, historical data such as execution logs, statuses, and any errors are available for review in the Operator Navigator. However, keep in mind that the history will be purged based on the Keep Log History (days) setting.

15. Where can I find more detailed information about Load Plan execution?

• You can refer to the Monitoring Integration Processes and Running Integration Processes chapters in the Oracle Data Integrator documentation for further information on Load Plan execution, monitoring, and troubleshooting.