Introduction to Operator Navigator

Monitoring Integration Processes 21-7

21.2.5 Handling Failed Load Plans

When a Load Plan ends in error, review the sessions that have failed and caused the Load Plan to fail. Fix the source of the session failure. You can restart the Load Plan instance. See Section 20.7, Restarting a Load Plan Run for more information. Note that it will restart depending on the Restart Type defined on its steps. See Section 14.2.4, Handling Load Plan Exceptions and Restartability for more information.

21.2.6 Reviewing Successful Load Plans

When your Load Plan ends successfully, you can review the execution statistics from the Load Plan run editor. You can also review the statistics for each session started for this Load Plan in the session editor. To review the Load Plan run execution statistics: 1. In the Operator Navigator, identify the Load Plan run to review. 2. Double click the Load Plan run. The corresponding editor opens. 3. The record and execution statistics are displayed on the Steps tab.

21.3 Managing your Executions

Managing your development executions takes place in Operator Navigator. You can manage your executions during the execution process itself or once the execution has finished depending on the action that you wish to perform. The actions that you can perform are: ■ Managing Sessions ■ Managing Load Plan Executions ■ Managing the Log ■ Managing Scenarios and Load Plans ■ Managing Schedules

21.3.1 Managing Sessions

Managing sessions involves the following tasks ■ New sessions can be created by executing run-time objects or scenarios. See Chapter 20, Running Integration Processes for more information on starting sessions. ■ Sessions in progress can be aborted. How to stop sessions is covered in Section 20.5, Stopping a Session . ■ Sessions failed, or stopped by user action can be restarted. Restarting sessions is covered in Section 20.4, Restarting a Session . In addition to these tasks, it may be necessary in production to deal with stale sessions. 21-8 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

21.3.1.1 Cleaning Stale Sessions

Stale sessions are sessions that are incorrectly left in a running state after an agent or repository crash. The Agent that started a session automatically detects when this session becomes stale and changes it to Error status. You can manually request specific Agents to clean stale sessions in Operator Navigator or Topology Navigator. To clean stale sessions manually:

1. Do one of the following:

■ From the Operator Navigator toolbar menu, select Clean Stale Sessions. ■ In Topology Navigator, from the Physical Architecture accordion, select an Agent, right-click and select Clean Stale Sessions. The Clean Stale Sessions Dialog opens.

2. In the Clean Stale Sessions Dialog specify the criteria for cleaning stale sessions:

■ From the list, select the Agents that will clean their stale sessions. Select Clean all Agents if you want all Agents to clean their stale sessions. ■ From the list, select the Work Repositories you want to clean. Select Clean all Work Repositories if you want to clean stale sessions in all Work Repositories.

3. Click Clean to start the cleaning process.

21.3.2 Managing Load Plan Executions

Managing Load Plan Executions involves the following tasks: ■ New Load Plan Instances and Runs can be created by executing Load Plans. See Section 20.6, Executing a Load Plan for more information on starting Load Plans. ■ Load Plan Runs in progress can be aborted. How to stop Load Plan runs is covered in Section 20.8, Stopping a Load Plan Run . ■ Load Plan Runs failed, or stopped by user action can be restarted. Restarting Load Plan Runs is covered in Section 20.7, Restarting a Load Plan Run .

21.3.3 Managing the Log

Oracle Data Integrator provides several solutions for managing your log data: ■ Filtering Sessions to display only certain execution sessions in Operator Navigator ■ Purging the Log to remove the information of past sessions ■ Organizing the Log with Session Folders ■ Exporting and Importing Log Data for archiving purposes

21.3.3.1 Filtering Sessions

Filtering log sessions allows you to display only certain sessions in Operator Navigator, by filtering on parameters such as the user, status or duration of sessions. Sessions that do not meet the current filter are hidden from view, but they are not removed from the log. To filter out sessions: