My Oracle Support Banner

OdiPurgeLog With "-TODATE" Option Doesn't Remove All Sessions as Expected (Doc ID 2434251.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Oracle Data Integrator - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) 12.2.1, when running the tool OdiPurgeLog with the "-TODATE" option, any sessions that have no "Start" date but do have an "End" date are not caught by the OdiPurgeLog, and therefore are not deleted.

The expectation is that these sessions would be deleted.

The issue can be reproduced at will with the following steps:

  1. Create a package using:

    OdiPurgeLog "-PURGE_TYPE=ALL" "-TODATE=2018/04/30 02:03:57" "-PURGE_REPORTS=YES"

  2. Create a scenario and execute in an environment where there are sessions without an "End" date
  3. Run the scenario and observe the issue

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.