At the core, ODI knowledge modules are templates of code that will be leveraged for data integration tasks: they pre-define data integration steps that are required to extract, load, stage - if needed - and integrate data.

Several types of Knowledge Modules are available, and are grouped in families for Loading operations (LKMs), Integration operations (IKMs), Data Control operations (CKMs), and more.

Through its recent acquisition of GoldenGate Software, Oracle has accelerated its product strategy to deliver a comprehensive data integration platform and increase uptime for customers' mission-critical systems. But, how can businesses profit from Oracle GoldenGate products? How does Oracle GoldenGate complement existing Oracle deployments?

To answer these questions and more, join Hasan Rizvi, Senior Vice President, Oracle Fusion Middleware and Juan Loaiza, Senior Vice President, Oracle Systems Technology in a live Webcast on Tuesday, November 10th at 8:00am PT (11:00am ET).

I have come across two serious issues when loading data from Excel into Oracle Data Integrator. These are not related to ODI, but are shortcomings of the Microsoft Excel ODBC driver. Both issues are explained on Metalink:

To read the entire article at its source, please refer to ODI Snippets: Oracle Data Integrator, Excel data types, and limitations of the MS Excel ODBC driver.

The posts in this series assume that you have some level of familiarity with ODI. The concepts of Datastore, Model and Logical Schema are used here assuming that you understand them in the context of ODI.

Oracle Data Integrator (ODI) is  - product from Sunopsis acquired by Oracle in 2006 and now part of Oracle Fusion Middleware Family.

In this article entitled "Developing a Knowledge Module in Oracle Data Integrator", Uli Bethke outlines what Knowledge Modules (KMs) are and how to customize and build an Integration Knowledge Module.

Uli writes: