Using Load Plans in Production FAQS

1. What is the purpose of using Load Plans in production?

• Load Plans in production help automate and orchestrate complex data integration tasks.
• They allow for scheduling, execution, monitoring, and management of multiple integration steps, ensuring a smooth flow of data operations across environments.

2. How do I schedule a Load Plan in production?

• You can schedule a Load Plan in production by using the Scheduler functionality in Oracle Data Integrator (ODI).
• The scheduler allows you to define the timing and frequency of when the Load Plan should run automatically.

3. Can I monitor the execution of Load Plans in production?

• Yes, you can monitor the execution of Load Plans using the Operator Navigator.
• It provides real-time information on the status, progress, and results of the Load Plan execution.

4. How do I stop a running Load Plan in production?

• If a Load Plan is running and you need to stop it, you can do so from the Operator Navigator by selecting the Load Plan instance and choosing the Stop or Abort option.

5. How can I export a Load Plan for use in another environment?

• To export a Load Plan, select the Load Plan you want to export, right-click, and choose the Export option.
• You can export a single Load Plan or multiple Load Plans at once.
• If you select Export child objects, all associated steps, schedules, and variables are exported as well.

6. Do I need to export scenarios used in the Load Plan separately?

• Yes, scenarios referenced by a Load Plan are not included in the Load Plan export.
• You need to export the scenarios separately using the Exporting Scenarios method.

7. How do I import a Load Plan into a development or production repository?

• In a development environment, you can import Load Plans using either Designer Navigator or Operator Navigator.
• In an execution repository (production), Operator Navigator is used for importing Load Plans.

8. How can I manage different versions of Load Plans in production?

• Load Plans can be versioned using Version Control.
• You can deploy and promote different versions to production to manage changes and ensure proper deployment strategies.

9. Can I import multiple Load Plans at once?

• Yes, you can import multiple Load Plans simultaneously by selecting multiple Load Plans during the import process.
• Make sure that any child objects, such as steps and schedules, are also imported.

10. What happens if I need to modify a Load Plan after it has been exported?

• Once a Load Plan is exported, you can modify it in the target repository (either development or production).
• If you need to make changes to the Load Plan in the original environment, you can re-export the modified version and import it back into the desired repository.

11. How do I handle Load Plans across different environments?

• To move Load Plans across environments, use the Export and Import procedures to transfer the Load Plans between development and production repositories.
• Ensure that all dependencies, such as scenarios and variables, are also transferred.

12. Can I version a Load Plan in a development environment?

• Yes, Load Plans can be versioned in both development and production environments.
• Versioning allows you to track changes, rollback if needed, and maintain different iterations of a Load Plan.

13. Can I stop a Load Plan that is scheduled in production?

• Yes, if a Load Plan is scheduled but hasn't yet run, you can modify or cancel the schedule from the Scheduler interface.
• If the Load Plan is already running, you can stop it via the Operator Navigator.

14. How do I ensure all dependencies are included when exporting a Load Plan?

• When exporting a Load Plan, make sure to select Export child objects to include all child steps, schedules, and variables.
• However, note that scenarios referenced by the Load Plan are not exported, so you must export them separately.

15. What if I need to restart a failed Load Plan in production?

• If a Load Plan fails, you can restart it manually from the Operator Navigator.
• You can also check the execution logs to identify the issue and re-execute the plan.

Using Load Plans in Production

1. Scheduling and Running Load Plans in Production

• Scheduling Load Plans: Schedule the Load Plans to run at specific times or intervals based on your production needs.
• Starting Load Plans: Initiate Load Plans from Designer or Operator Navigator.
• Monitoring Load Plans: Use the Operator Navigator to track the execution status and progress of Load Plans.
• Stopping Load Plans: If needed, stop a Load Plan during execution from the Operator Navigator.
• Restarting Load Plans: You can restart a Load Plan if it fails or needs to be re-executed, following the instructions in the Running Integration Processes chapter in the Administering Oracle Data Integrator manual.

2. Exporting Load Plans

• Exporting a Single Load Plan: To export a single Load Plan, follow the procedure described in the Exporting One ODI Object documentation.
• Exporting Multiple Load Plans: To export multiple Load Plans at once, follow the Export Multiple ODI Objects guidelines.
• Export Child Objects: When exporting a Load Plan, ensure that child objects such as child steps, schedules, and variables are also exported by selecting the Export child objects option.
• Note: The export process does not include the scenarios referenced by the Load Plan. You need to export the scenarios separately, as detailed in the Exporting Scenarios section.

3. Importing Load Plans

• Importing into a Development Repository: In a development environment, use either the Designer Navigator or Operator Navigator to import Load Plans.
• Importing into an Execution Repository: Only Operator Navigator is available for importing Load Plans in the execution repository.
• Standard Import Method: Follow the Importing Objects procedure to import Load Plans.
• Note: Just like with exporting, scenarios used in the Load Plan must be imported separately.

4. Versioning Load Plans

• Version Control: Load Plans can be versioned to manage different versions in production environments.
• Deploy and Promote with Versions: Deploy Load Plans to production by managing them through version control, and promote specific versions as needed.
• For more details on versioning and solutions, refer to Using Version Control (Legacy Mode).

Key Points:

• Scheduling and Running Load Plans: Ensure you understand how to schedule, start, monitor, stop, and restart Load Plans in production environments.
• Exporting and Importing Load Plans: Use these steps to deploy Load Plans across different repositories, ensuring all necessary objects (such as child steps and variables) are included in the transfer.
• Versioning for Deployment: Utilize version control to manage Load Plan versions during deployment and production promotion.

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.