My Oracle Support Banner

Possible Approaches For The Implementation Of ODI CDC Features With The Oracle eBusiness Suite (Doc ID 1285904.1)

Last updated on JUNE 16, 2022

Applies to:

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

Purpose

A certain number of challenges are encountered when using the Oracle Data Integrator (ODI) Changed Data Capture (CDC) feature with Oracle eBusiness Suite.

In particular, Oracle eBusiness Suite implements tables with very long table names. Moreover, many tables have names that differ only by the last 2, 3 or 4 characters. This contrasts with conventional best practices for the Oracle database for which table names can have a maximum of 30 character.

For example:

At runtime of an Integration Interface set up to extract the journalized information by the CDC procedures, ODI recognizes that the CDC infrastructure is available by checking for the presence of the tables and views. If these objects are not named according to the CDC conventions, ODI assumes that CDC is not available… and will prevent the successful execution of the Integration Interface.

The creation of database synonyms on the table could provide a possible alternative to avoid the above issue. The J$ tables and views could match the name of the synonym, and the name of the synonym may be shorter than that of the table on which this synonym is set. However, the ODI CDC Knowledge Modules set up to use the LogMiner, and, furthermore, Oracle Logminer cannot function with database synonyms.

It is also important to understand that when the ODI Journalizing Knowledge Module (JKM) is executing, there is no notion of source or target table. The ODI Substitution Method called odiRef.getTable returns only information concerning the table being journalized (Table ID…) during this run. (A possibility would be to take advantage of the fact that an ODI datastore is described by a resource name and a name. One of these two elements could have been used as the database synonym name (for the J$ tables) while the other one for Oracle LogMiner. (However, only the resource name is available from the JKM).

Scope

This article is for engineers who wish to develop ODI Integration Interfaces using its CDC features and Oracle eBusiness Suite applications as their source databases.

This requires a good knowledge of the development and /or modification of Oracle Data Integrator (ODI) Knowledge Modules.

Details

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
Purpose
Scope
Details
 1. Options available to manage differences between table name and database synonym names
 1.1 FlexFields
 1.2 Jython Variable and Database query
 2. Locations in the Knowledge Modules where the code must be customized
 3. Final implementation and solution

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