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.