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.