Load Plans Load Plan Executions

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 archived in the work repository. It is advised to perform a purge regularly. This purge can be automated using the OdiPurgeLog tool in a scenario. To purge the log:

1. From the Operator Navigator toolbar menu select Connect Navigator Purge

Log... The Purge Log editor opens. 2. In the Purge Log editor, set the criteria listed in Table 21–3 for the sessions or Load Plan runs you want to delete. Table 21–3 Purge Log Parameters Parameter Description Purge Type Select the objects to purge. From ... To Sessions andor Load Plan runs in this time range will be deleted. When you choose to purge session logs only, then the sessions launched as part of the Load Plan runs are not purged even if they match the filter criteria. When you purge Load Plan runs, the Load Plan run which matched the filter criteria and the sessions launched directly as part of the Load Plan run and its childgrand sessions will be deleted. Context Sessions andor Load Plan runs executed in this context will be deleted.