Troubleshooting Load Plans

A load plan must be restarted when it has stopped with an error. An alternate case where restart may be required is when a load plan is not doing anything at all, for example, when a load plan is executed and nothing has changed after 30 minutes. The following checklist can be used to assist in troubleshooting a non-responsive load plan.

  1. Check the maximum number of sessions set to run against the agent.

    In ODI Operator, verify that the number of sessions running is equal to the maximum. If so, then the other sessions are waiting for the running sessions to complete. Proceed to the next step.

  2. Clean out stale sessions.

    Stale sessions are sessions that are incorrectly left in a running state after an agent or repository crash. If an agent crashes or loses its connection the repository after it has started a session, it is not be able to update the status of the session in the repository, and such a session becomes stale. Until the stale session is cleaned it shows up as running in the repository but actually is not.

    Stale sessions are cleaned in multiple ways. Some examples are listed below:

    • You can manually request specific agents to clean stale sessions in Operator Navigator or Topology Navigator.

    • Stale sessions are cleaned when you restart an agent.

    • When an agent starts any new session, it checks for and resolves stale sessions. However, if the agent has lost connection to the repository, then it cannot clean stale sessions.

  3. Check if the agent is alive.

    To test the agent to see if it is running and still has a connection to the repository, open it in the Topology Navigator in ODI Studio and select the Test tab. If the agent test fails, then restart the agent after fixing the issue.

  4. Verify that the ODI Repository and the server hosting it are running and have not experienced a failure.
  5. If your load plan is in error and you have verified all of the above, then restart the load plan.

    Note:

    When you restart the load plan, set the Log Level to 6. Log Level 6 will enable you to see variable values resolved in session logs.