Using WS-Addressing Managing Executions Using Web Services

21-4 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator When finished, a session takes the status of the last executed step Done or Error. When finished, the step, takes the status of the last executed task Except if the task returned a Warning. In this case, the step takes the status Done. A Load Plan is successful status Done when all its child steps have been executed successfully. It is in Error status when at least one of its child steps is in error and has raised its exception to the root step.

21.2 Monitoring Executions Results

In Oracle Data Integrator, an execution results in a session or in a Load Plan run if a Load Plan is executed. A session is made up of steps which are made up of tasks. Sessions are viewed and managed in Operator Navigator. Load Plan runs appear in the Operator Navigator. To review the steps of a Load Plan run, you open the editor for this run. The sessions attached to a Load Plan appear with the rest of the sessions in the Operator Navigator.

21.2.1 Monitoring Sessions

To monitor your sessions:

1. In the Operator Navigator, expand the Session List accordion.

2. Expand the All Executions node and click Refresh in the Navigator toolbar.

3. Optionally, activate a Filter to reduce the number of visible sessions. For more

information, see Section 21.3.3.1, Filtering Sessions . Table 21–2 Status Values Status Name Status Icon for Sessions Status Icon for Load Plans Status Description Done The Load Plan, session, step or task was executed successfully. Done in previous run The Load Plan step has been executed in a previous Load Plan run. This icon is displayed after a restart. Error The Load Plan, session, step or task has terminated due to an error. Running The Load Plan, session, step or task is being executed. Waiting The Load Plan, session, step or task is waiting to be executed. Warning Sessions and tasks only ■ For Sessions: The session has completed successfully but errors have been detected during the data quality check. ■ For Tasks: The task has terminated in error, but since errors are allowed on this task, this did not stop the session. Queued Sessions only The session is waiting for an agent to be available for its execution Monitoring Integration Processes 21-5 4. Review in the list of sessions the status of your sessions.

21.2.2 Monitoring Load Plan Runs

To monitor your Load Plan runs: 1. In the Operator Navigator, expand the Load Plan Executions accordion.

2. Expand the All Executions node and click Refresh in the Navigator toolbar.

3. Review in the list the status of your Load Plan run. 4. Double-click this Load Plan run to open the Load Plan Run editor. 5. In the Load Plan Run editor, select the Steps tab. 6. Review the state of the Load Plan steps. On this tab, you can perform the following tasks: ■ Click Refresh in the Editor toolbar to update the content of the table. ■ For the Run Scenario steps, you can click in the Session ID column to open the session started by this Load Plan for this step.

21.2.3 Handling Failed Sessions

When your session ends in error or with a warning, you can analyze the error in Operator Navigator. To analyze an error: 1. In the Operator Navigator, identify the session, the step and the task in error. 2. Double click the task in error. The Task editor opens. 3. On the Definition tab in the Execution Statistics section, the return code and message give the error that stopped the session. 4. On the Code tab, the source and target code for the task is displayed and can be reviewed and edited. 5. On the Connection tab, you can review the source and target connections against which the code is executed. You can fix the code of the command in the Code tab and apply your changes. Restarting a Session is possible after performing this action. The session will restart from the task in error. Note: Fixing the code in the session’s task does not fix the source object that was executed interface, procedure, package or scenario. This source object must be fixed in Designer Navigator and the scenario if any must be regenerated. Modifying the code within the session is useful for debugging issues. WARNING: When a session fails, all connections and transactions to the source and target systems are rolled back. As a consequence, uncommitted statements on transactions are not applied.