Oracle Data Integration Sample Code
Unless explicitly identified as such, the sample code here is not certified or supported by Oracle; it is intended for educational or testing purposes only.
Download |
Description |
Name |
|---|---|---|
| Loads multiple files using Oracle external table. Also incorporates support for the external table preprocessor. | LKM Files to Oracle (External Table) | |
| This LKM loads flat file data into Oracle by using the SQL*LOADER utility. The original LKM File to SQLLDR from ODI 11.1.1.3 was extended to include EBCDIC Data. Does not have the issues related to older versioned :code-sample ID S550: Community Knowledge Module: LKM EBCDIC File to Oracle (SQLLDR) | Community Knowledge Module: LKM File to Oracle (SQLLDR) with EBCDIC Option | |
| Illustration of how to generate SQL components such as Oracle Table Functions from within ODI. | SQL IKM for Oracle Table Function | |
| Bulk loads data into Oracle - from any database | ODI KM: LKM SQL to Oracle (Bulk - External Table).xml | |
| These scripts aim to accelerate and automate installation/configuration process of vanilla SOA suite, AIA Foundation Pack and certain set of PIPs (O2C, Comms PIPs, MDM PIPs) for clustered environment. This version has following updates : - various bug fixes - more flexible patch scripts - support for 10.1.3.5 MLR #2 - support for IPS2 version of Comms PIPs / MDM PIPs - support for Design to Release PIP | AIA 2.x Install Accelerator Scripts | |
| These scripts aim to accelerate and automate installation/configuration process of vanilla SOA suite, AIA Foundation Pack and certain set of PIPs (O2C, Comms PIPs, MDM PIPs) for clustered environment. | AIA 2.x Installation Accelerator Scripts | |
| These scripts aim to accelerate and automate installation/configuration process of vanilla SOA suite, AIA Foundation Pack and certain set of PIPs (O2C, Comms PIPs, MDM PIPs) for clustered environment. | AIA 2.x Installation Accelerator Scripts | |
| These scripts aim to accelerate and automate installation/configuration process of vanilla SOA suite, AIA Foundation Pack and certain set of PIPs for clustered environment. | AIA 2.x Installation Accelerator Scripts | |
| High performance file to file processing Knowledge Module for Oracle Data Integrator that generates Perl code with the optional capability of leveraging Hadoop parallel processing framework to further increase performance / scalability. | IKM File to File (Perl) integration with experimental Hadoop parallel processing | |
| Lets users build temporary interfaces that represent inline views or SQL as a source. An option on the IKM captures the query when applied to a temporary interface and the temporary interface is nested in another interface with the derived sub select property set. | IKM SQL as a Source | |
| The collection of downloads described on the OWB Utility Exchange here: //www.oracle.com/technetwork/developer-tools/warehouse/owbexchange-099994.html | Warehouse Builder Utility Exchange Downloads | |
1.) Added an Option "USE_CREATE_TABLE_FOR_APPEND" to Fully Seed very large tables (over 200 GB), right upon the creation of a table. In Exadata, it is better to use a Create Select as statement, than an Insert into a I$ table and then a subsequent Insert into the target table, when seeding target data, for CDC with Golden Gate. Also Ensure that "CREATE_PARALLEL_HINT" is set. 2.) Added the ability to seed the Target table using a row limit. Set USE_ROW_LIMIT to true and a sample size for ROW_LIMIT. 3.) Defaulted OPTIMIZER_HINT to use parallelism e.g. /*+ parallel(table1,64) parallel(table2,64) */ 4.) Added alter session parallel statements |
IKM SQL Control Append_BIG_DATA | |
| Added a detection strategy which was not included in the original KM. The Detection Strategies are NONE, MINUS, POST_FLOW, NOT EXISTS and a new one MERGE. The default MINUS was not performant on Exadata. Use NOT EXISTS instead. If no Staging is required, use MERGE. When MERGE is used, Flow Control must be set to false. Upon a Detection Strategy of Merge, no I$ tables will be created. Instead the Merge Statement will contain the entire source select. This is very performant on Exadata when the Source and Target are on the same database. | IKM Oracle Incremental Update (MERGE) For Exadata | |
| ODI developers seeking sql function portability will use the user defined functions (UDF) in their sql expressions. | Oracle Data Integrator 11g UDF Sample | |
| Supports calling RESTful web services from inside an OWB code template mapping. | Code Template LCT_RESTWS_TO_ORACLE.mdl | |
| The SQL Developer reports are primarily reports on the OWB runtime, there are some simple reports for the design and data quality, but the reports are mostly centered on the runtime; analysis of map/flow timings, audit details etc. | OWB SQL Developer Reports | |
| This sample code package includes example code for performing the following using the Oracle Data Integrator API: - Connection and Authentication - Start and Restart Scenario - Get Session Status - Create Folders - Interface Consultation, Creation and Edition - Session Monitoring - KM import and find - Create Master and Work Repositories - Upgrade Master and Work Repositories - Create Agent and Context | Oracle Data Integrator 11gR1 Java API Code Samples Package | |
| - Integrates data in any AINSI-SQL92 compliant database target table in incremental update mode. - provide the ability to integrate data from a staging area to a target and be able to know precisely the state of each row processed | Community Knowledge Module: IKM SQL Incremental Update (row by row) | |
| Moves data from any generic JDBC SQL source to generic JDBC SQL target, row by row. | Community Knowledge Module: LKM SQL to SQL (row by row) | |
| Loads data from an MVS source into Oracle. | Community Knowledge Module: LKM VSAM to Oracle (JCL IDCAMS - SQLLDR) | |
| Loads BLOB and standard data from any SQL92 database to an Oracle target database. | Community Knowledge Module: LKM SQL to Oracle (CLOB) | |
| Loads data from any ISO-92 database to any ISO-92 compliant target database. Specially modified for dealing with CLOB and BLOB values. | Community Knowledge Module: LKM SQL to Oracle Lob | |
| This LKM loads flat file data into Oracle by using the SQL*LOADER utility. | Community Knowledge Module: LKM File to Oracle (SQLLDR)-Cyrillic | |
| This LKM loads flat file data into Oracle by using the SQL*LOADER utility. Call to SQL*LOADER is made and stdout and stderr are redirected into log files. A specific log file is created by SQL*LOADER. Oracle recommends 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 file. | Community Knowledge Module: LKM EBCDIC File to Oracle (SQLLDR) | |
| Create and Exexute a JCL to download a table in a sequentilal file in MVS system - transfer a sequential file to a Agent machine using a FTP command. - Loads data from a DB2 to an Oracle Database using the SQL*LOADER utility | Community Knowledge Module: LKM DB2(MVS) to Oracle (JCL Unload - SQLLDR) | |
| - This module reads selected data from the Attunity Stream staging area of Attunity Streams and writes the result into the target temporary table, which is created dynamically. - Loads data to any ISO-92 compliant target database. | Community Knowledge Module: LKM Attunity to SQL | |
| - This JKM provides consistent journalizing procedures for Oracle tables. - This KM uses Oracle Streams to capture data changes on the source tables. | Community Knowledge Module: JKM Oracle 10g Consistent (Streams) | |
| - Integration Knowledge Module - Integration from Teradata to Teradata using BTEQ. - Ability to use INSERT, UPSERT, UPDATE or DELETE BTEQ Scripts (specified with the OPERATION_MODE option) | IKM Teradata to Teradata (BTEQ) | |
| This KM is a simple/limited KM which is for use when transferring data from a single table in an MS SQL Server database direct to the same table (name, columns) in Oracle. the transfer is effected using BCP to take the data out of SQL Server, and Oracle's EXTERNAL TABLE functionality to get the data into the target table. No provision is made to select on Journalized data. No provision is made to join the source tables. It does not check to ensure that generated table or index names are within the limits of the technology. | Community Knowledge Module: IKM SQL to Oracle (SQLUnload-EXTTABLE) | |
| - Loads a file from a Postgres source - The file is populated in truncate / insert mode. - A flow table is created Target technology: FILE Source technology: POSTGRESSQL | Community Knowledge Module: IKM Postgres to File | |
| Integrates data into an Oracle target table in incremental update mode. Inexistent rows are inserted; already existing rows are updated. Data can be controlled. Erroneous data is isolated in the error table and can be recycled. When using this module with a journalized source table, it is possible to synchronize deletions. | IKM Oracle Incremental Update Lob | |
| Integration Knowledge Module - Integrates data in Oracle database target table in incremental update mode. - Non-existent rows are inserted; existing rows are updated. - Data can be controlled. Invalid data is isolated in the Error Table and can be recycled. - When using this module with a journalized source table, it is possible to synchronize deletions. - This operates without using the MINUS clause on the Insert flow into I$ step, it instead identifies the rows which do not need to be updated with an update statement. | IKM Oracle Incremental Update (no MINUS) | |
| Integration Knowledge Module - Pivot data from one row to many rows | IKM Oracle (Pivot) | |
| Integration Knowledge Module - Pivot data from one row to many rows | Community Knowledge Module: IKM Oracle (Generic Pivot) | |
| Loading Knowledge Module - Loads data from a file to an Oracle Database using the SQL*LOADER utility - Call to SQL*LOADER is made through a Jython call to an Operating System command. - A specific log file is created by SQL*LOADER. Oracle recommends looking at this file in case of error. | IKM File to Oracle (SQLLDR) DIRECT APPEND Multiple | |
| This KM is a simple/limited KM which is for use when transferring data from a file direct to a table in Oracle. It uses Oracle's EXTERNAL TABLE functionality to get the data into the target table. It does not check to ensure that generated table or index names are within the limits of the technology. | Community Knowledge Module: IKM File to Oracle (ExtTable) Append | |
| COMPATIBILITY: ODI 10.1.3.4.4 and above; OWB 11.2 NOTE: Not officially supported. DESCRIPTION - This JKM provides consistent journalizing procedures for Oracle tables. - This KM uses Oracle Streams to capture data changes on the source tables. | Community Knowledge Module: JKM Oracle 10g Consistent (Streams) | |
| Creating a Warehouse Builder process flow with activities to ftp a file from linux to windows and to test for success. | FTP Windows to Linux: Process Flow Example | |
| Integrate data from file source to file target using Perl. | Knowledge Module: IKM File to File (Perl) | |
A collection of knowledge modules for use with ODI 10.1. Unsupported, but should provide a starting point for developing more robust solutions for these use cases. Includes: KM_CKM_Mysql_3.0_4.0_version_1.0.0.0.xml
|
Knowledge Modules: MySQL (Experimental) | |
| This example is intended to supplement the ALDSP 3.0 documentation for update maps. | CustomerOrders update map example |