My Oracle Support Banner

Setting up An ODI Standalone Agent To Handle Purging Of Outdated Data From ODI Staging Tables? (Doc ID 1676312.1)

Last updated on DECEMBER 12, 2019

Applies to:

Oracle Knowledge - Version 8.5 and later
Information in this document applies to any platform.
For Oracle Analtyics the stand alone ODI agent is required. And the setup for log purge is below.


According to the Oracle Knowledge Analytics Administration Guide, on page 41 it is stated:

"Analytics includes an automated process to remove outdated data from the staging database tables. The purging process is an ODI package that automatically deletes data from various tables. It purges data from a defined set of tables according to the schedule described in “The Default Purging Interval” on page 44.

You configure and schedule the purging process using an ODI data management agent. You enable, schedule and start the ODI agent using the process described in “Enabling and Scheduling an ODI Data Management Agent” on page 42."

From ODI_HOME\oracledi\agent\bin

on sqlserver
startcmd.bat  OdiPurgeLog "-PURGE_TYPE=LOAD_PLAN_RUN" "-CONTEXT_CODE=GLOBAL,DEVELOPMENT" "-AGENT_NAME=put your agent name here"
startcmd.bat OdiPurgeLog "-FROMDATE=2001/03/25 00:00:00" "-TODATE=2001/08/31 21:59:00"

on linux  OdiPurgeLog "-PURGE_TYPE=LOAD_PLAN_RUN" "-CONTEXT_CODE=GLOBAL,DEVELOPMENT" "-AGENT_NAME=put your agent name here"
or OdiPurgeLog "-FROMDATE=2001/03/25 00:00:00" "-TODATE=2001/08/31 21:59:00"

Within the ODI documentation Developer's Guide for Oracle Data Integrator, it is stated:

"The Oracle Data Integrator agents exists in two flavors: standalone agent and Java EE agent.

A standalone agent runs in a separate Java Virtual Machine (JVM) process. It connects to the work repository and to the source and target data servers via JDBC. Standalone agents can be installed on any server with a Java Virtual Machine installed. This type of agent is more appropriate when you need to use a resource that is local to one of your data servers (for example, the file system or a loader utility installed with the database instance), and you do not want to install a Java EE application server on this machine.

A Java EE agent is deployed as a web application in a Java EE application server (for example Oracle WebLogic Server or IBM WebSphere). The Java EE agent can benefit from all the features of the application server (for example, JDBC data sources or clustering for Oracle WebLogic Server). This type of agent is more appropriate when there is a need for centralizing the deployment and management of all applications in an enterprise application server, or when you have requirements for high availability."

The Standalone Agent is required.

Questions and Answers

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
Questions and Answers

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