2-2 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator
Table 2–1 Oracle Database Knowledge Modules
Knowledge Module Description
RKM Oracle Reverse-engineers tables, views, columns, primary keys, non unique
indexes and foreign keys. JKM Oracle 10g Consistent Streams
Creates the journalizing infrastructure for consistent set journalizing on Oracle 10g tables, using Oracle Streams.
JKM Oracle 11g Consistent Streams Creates the journalizing infrastructure for consistent set journalizing
on Oracle 11g tables, using Oracle Streams. JKM Oracle Consistent
Creates the journalizing infrastructure for consistent set journalizing on Oracle tables using triggers.
JKM Oracle Consistent Update Date Creates the journalizing infrastructure for consistent set journalizing
on Oracle tables using triggers based on a Last Update Date column on the source tables.
JKM Oracle Simple Creates the journalizing infrastructure for simple journalizing on
Oracle tables using triggers. JKM Oracle to Oracle Consistent OGG
Creates and manages the ODI CDC framework infrastructure when using Oracle GoldenGate for CDC. See
Chapter 29, Oracle GoldenGate
for more information. CKM Oracle
Checks data integrity against constraints defined on an Oracle table. LKM File to Oracle EXTERNAL TABLE
Loads data from a file to an Oracle staging area using the EXTERNAL TABLE SQL Command.
LKM File to Oracle SQLLDR Loads data from a file to an Oracle staging area using the
SQLLoader command line utility. LKM MSSQL to Oracle BCP SQLLDR
Loads data from a Microsoft SQL Server to Oracle database staging area using the BCP and SQLLoader utilities.
LKM Oracle BI to Oracle DBLINK Loads data from any Oracle BI physical layer to an Oracle target
database using database links. See Chapter 18, Oracle Business
Intelligence Enterprise Edition for more information.
LKM Oracle to Oracle DBLINK Loads data from an Oracle source database to an Oracle staging area
database using database links. LKM Oracle to Oracle datapump
Loads data from an Oracle source database to an Oracle staging area database using external tables in the datapump format.
LKM SQL to Oracle Loads data from any ANSI SQL-92 source database to an Oracle
staging area. LKM SAP BW to Oracle SQLLDR
Loads data from SAP BW systems to an Oracle staging using SQLLoader utilities. See the Oracle Fusion Middleware Application
Adapters Guide for Oracle Data Integrator for more information. LKM SAP ERP to Oracle SQLLDR
Loads data from SAP ERP systems to an Oracle staging using SQLLoader utilities. See the Oracle Fusion Middleware Application
Adapters Guide for Oracle Data Integrator for more information. IKM Oracle AW Incremental Update
Integrates data in an Oracle target table in incremental update mode and is able to refresh a Cube in an Analytical Workspace. See
Chapter 23, Oracle OLAP for more information.
IKM Oracle Incremental Update Integrates data in an Oracle target table in incremental update mode.
IKM Oracle Incremental Update MERGE Integrates data in an Oracle target table in incremental update mode,
using a MERGE statement. IKM Oracle Incremental Update PL SQL
Integrates data in an Oracle target table in incremental update mode using PLSQL.
Oracle Database 2-3
2.2 Installation and Configuration
Make sure you have read the information in this section before you start using the Oracle Knowledge Modules:
■
System Requirements and Certifications
■
Technology Specific Requirements
■
Connectivity Requirements
2.2.1 System Requirements and Certifications
Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum
installation requirements for the products you are installing.
The list of supported platforms and versions is available on Oracle Technical Network OTN:
http:www.oracle.comtechnologyproductsoracle-data-integrator index.html
.
2.2.2 Technology Specific Requirements
Some of the Knowledge Modules for Oracle use specific features of this database. This section lists the requirements related to these features.
2.2.2.1 Using the SQLLoader Utility
This section describes the requirements that must be met before using the SQLLoader utility with Oracle database.
■
The Oracle Client and the SQLLoader utility must be installed on the machine running the Oracle Data Integrator Agent.
■
The server names defined in the Topology must match the Oracle TNS name used to access the Oracle instances.
IKM Oracle Multi Table Insert Integrates data from one source into one or many Oracle target tables
in append mode, using a multi-table insert statement MTI. IKM Oracle Slowly Changing Dimension
Integrates data in an Oracle target table used as a Type II Slowly Changing Dimension.
IKM Oracle Spatial Incremental Update Integrates data into an Oracle 9i or above target table in incremental
update mode using the MERGE DML statement. This module supports the SDO_GEOMETRY datatype.
IKM Oracle to Oracle Control Append DBLINK
Integrates data from one Oracle instance into an Oracle target table on another Oracle instance in control append mode.
This IKM is typically used for ETL configurations: source and target tables are on different Oracle instances and the interfaces staging
area is set to the logical schema of the source tables or a third schema. SKM Oracle
Generates data access Web services for Oracle databases. See Working with Data Services in the Oracle Fusion Middleware
Developers Guide for Oracle Data Integrator for information about how to use this SKM.
Table 2–1 Cont. Oracle Database Knowledge Modules
Knowledge Module Description
2-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator
■
A specific log file is created by SQLLoader. We recommend looking at this file in case of error. Control Files CTL, Log files LOG, Discard Files DSC and Bad
files BAD are placed in the work directory defined in the physical schema of the source files.
■
Using the DIRECT mode requires that Oracle Data integrator Agent run on the target Oracle server machine. The source file must also be on that machine.
2.2.2.2 Using External Tables
This section describes the requirements that must be met before using external tables in Oracle database.
■
The file to be loaded by the External Table command needs to be accessible from the Oracle instance. This file must be located on the file system of the server
machine or reachable from a Unique Naming Convention path UNC path or stored locally.
■
For performance reasons, it is recommended to install the Oracle Data Integrator Agent on the target server machine.
2.2.2.3 Using Oracle Streams
This section describes the requirements for using Oracle Streams Journalizing knowledge modules.
The following requirements must be met before setting up changed data capture using Oracle Streams:
■
Oracle Streams must be installed on the Oracle Database.
■
The Oracle database must run using a SPFILE only required for AUTO_ CONFIGURATION option.
■
The AQ_TM_PROCESSES option must be either left to the default value, or set to a value different from 0 and 10.
■
The COMPATIBLE option should be set to 10.1 or higher.
■
The database must run in ARCHIVELOG mode.
■
PARALLEL_MAX_SERVERS must be increased in order to take into count the number of Apply and Capture processes. It should be increased at least by 6 for
Standalone configuration, 9 for Low-Activity and 21 for High-Activity.
■
UNDO_RETENTION must be set to 3600 at least.
■
STREAMS_POOL_SIZE must be increased by 100MB for Standalone configuration, 236MB for Low-Activity and 548MB for High-Activity.
■
All the columns of the primary key defined in the ODI Model must be part of a SUPPLEMENTAL LOG GROUP.
■
When using the AUTO_CONFIGURATION knowledge module option, all the above requirements are checked and set-up automatically, except some actions
that must be set manually. See Using the Streams JKMs
for more information.
Note: It is recommended to review first the Changed Data Capture
chapter in the Oracle Database Data Warehousing Guide, which contains the comprehensive list of requirements for Oracle Streams.
