Scenarios Sessions Introduction to Monitoring

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: Monitoring Integration Processes 21-9

1. In the Operator Navigator toolbar menu, click Filter. The Define Filter editor

opens. 2. In the Define Filter Editor, set the filter criteria according to your needs. Note that the default settings select all sessions. ■ Session Number : Use blank to show all sessions. ■ Session Name : Use as a wildcard. For example DWH matches any session whose name begins with DWH. ■ Sessions execution Context ■ Agent used to execute the session ■ User who launched the session ■ Status : Running, Waiting etc. ■ Date of execution: Specify either a date From or a date To, or both. ■ Duration greater than a specified number of seconds

3. Click Apply for a preview of the current filter.

4. Click OK.

Sessions that do not match these criteria are hidden in the Session List accordion. The Filter button on the toolbar is activated. To deactivate the filter click Filter in the Operator toolbar menu. The current filter is deactivated, and all sessions appear in the list.

21.3.3.2 Purging the Log

Purging the log allows you to remove past sessions and Load Plan runs from the log. This procedure is used to keeping a reasonable volume of sessions and Load Plans