Load Plan Execution Lifecycle FAQS

1. What is a Load Plan Instance?
   A Load Plan Instance is created when you execute a Load Plan. It represents a unique execution of a Load Plan and is separate from the original Load Plan definition.
2. What happens when I run a Load Plan?
   When a Load Plan is executed, a Load Plan Instance is created, and the first Load Plan Run is triggered. Each subsequent execution attempt is treated as a new Load Plan Run under the same Load Plan Instance.
3. What is a Load Plan Run?
   A Load Plan Run refers to a specific execution attempt of a Load Plan Instance. If the Load Plan is restarted, a new Load Plan Run is created under the same Load Plan Instance. Each run is logged separately.
4. Can I run multiple instances of the same Load Plan?
   Yes, you can run multiple instances of the same Load Plan concurrently, provided the Concurrent Execution Control settings allow it. This is managed based on the Load Plan’s internal ID and configured settings.
5. Can I have more than one active run for a Load Plan Instance?
   No, a Load Plan Instance can only have one active run at a time. However, you can have multiple instances of the same Load Plan running at the same time if concurrency settings allow.
6. What is Concurrent Execution Control?
   Concurrent Execution Control determines how many instances of a Load Plan can be run at the same time. It is based on the Load Plan’s internal ID and its configuration settings.
7. How is the execution history of a Load Plan tracked?
   Each Load Plan Run is recorded in the system log. This allows you to track each execution attempt, whether it was successful, failed, or restarted.
8. What happens if I restart a Load Plan Run?
   If a Load Plan Run is restarted, a new Load Plan Run is created under the same Load Plan Instance. The original execution attempt and the restart are both recorded as separate runs in the log.
9. Can I schedule Load Plans for execution?
   Yes, Load Plans can be scheduled for automatic execution using the built-in scheduler or an external scheduler, which helps in automating the execution process.
10. How does Oracle Data Integrator manage Load Plan Runs?
    Each execution attempt of a Load Plan Instance is preserved as a different Load Plan Run. These runs are tracked and stored in logs, making it easy to review the execution status and history.
11. Can I modify a Load Plan while it's executing?
    Typically, you cannot modify an active Load Plan while it's executing. However, you can manage different instances of the same Load Plan with separate executions.
12. What are the log details for a Load Plan Run?
    Logs for each Load Plan Run include details such as:
• Execution start and end times.
• Status of the run (success, failure, or restart).
• Error messages (if applicable).