ODI - Staging Area (or Work area)

Card Puncher Data Processing


ODI Knowledge Modules often use temporary objects to:

  • stage temporary data for jobs optimization.
  • execute some rules

These temporary objects are always stored in a particular schema or directory called the Work Schema (or staging area).

These work schemas should be kept separate from the schema containing the application data (Data Schema).

Odi Designer Execute On


  • when the source is a flat file, and as such is not associated to an engine that supports operations (as concatenation, uppercase, …)
  • all components (except the triggers) of the journalizing infrastructure (like all Data Integrator temporary objects, such as integration, error and loading tables)

Objects and work tables prefix

Odi Work Schema

On the target data servers, you should almost certainly create a dedicated work schema. This will store:

  • Temporary tables and views created during the loading phase if the source data is not in the same server as the target (C$ tables)
  • Temporary tables created during the integration phase when using certain Integration Knowledge Modules (I$ tables)
  • Permanent Error tables created during Data Quality Control phase when using Check Knowledge Modules (E$ tables)
  • Permanent Journal tables, views and triggers created when the target is to be used as a source with Change Data Capture enabled by using Journalizing Knowledge Modules (J$ objects)

On “read-only” source data servers the following objects may be created depending on the way you want to address these servers:

  • Views during Load phases, when using certain Loading Knowledge Modules
  • Error tables when performing a “static” Data Quality Control (e.g. when controlling the data of a particular source schema independently of any load job)
  • Journal tables, views and triggers when using Change Data Capture on the sources.

Where is the Staging Area ?

The staging area (or Work area) is first define when you create a physical schema but you can change it in the interface properties

Odi Designer Interface Staging Area Target

Discover More
Odi Essbase Data Server
ODI - Adapter for Hyperion Essbase - Getting Started

installation of the sample essbase database file (the sources for the samples are delimited flat files) Five Knowledge Modules (KMs): RKM Hyperion Essbase—For reverse-engineering Essbase applications...
Odi Work Schema
ODI - CDC Journalizing Infrastructure

When the journals are started, the journalizing infrastructure (if not installed yet) is deployed or updated. When the journalizing knowledge module creates triggers, they are installed on the tables...
Card Puncher Data Processing
ODI - Datastore (Source and Target)

A datastore is a structure that allows data to be stored. It can be : a table, a file, a message queue or any other data structure accessible by middleware used by Oracle Data Integrator (JDBC/ODBC,...
Card Puncher Data Processing
ODI - Log / Debug

The trick is here is to use an rdbms logical schema as the staging area (e.g. sql server, oracle). Set the interface not to delete the temporary target. Run the interface, the first step will be to...
Odi Jkm Oracle
ODI - Setting up Journalizing/CDC

This is the basic process for setting up CDC on an Oracle Data Integrator data model. Each of these steps is described in more detail below. Set the CDC parameters Add the datastores to the CDC ...
Odi Sunopsis Memory Engine Jdbc
ODI - Sunopsis Engine

Oracle Data Integrator not only uses hsqldb for its demo environment. It is also used as the in memory database for the so called Sunopsis Memory Engine. When creating interfaces for sources and targets...
Odi Topology Create Physical Schema
ODI - The physical schema

When you create a data server, the physical schema windows appear automatically or right click on a data server, insert a physical schema. Fill in: the schema the work schema. ODI Knowledge Modules...

Share this page:
Follow us:
Task Runner