Oracle Database

Overview

With the Oracle component, you can produce fully customized Oracle Database data flows in Semarchy xDI.

The database structure can be fully reverse-engineered and stored in xDI Metadata. You can then use it when designing mappings and processes to adapt your business rules according to your requirements.

Third-party libraries

Due to licensing restrictions, we cannot distribute the Java libraries for this database. You must obtain them yourself.

After you have the necessary Oracle libraries, create a Oracle module for your project, and add the libraries to the module.

Supported features

Common features

Feature Description

Reverse

This technology can be reverse-engineered to xDI Metadata.

DDL/DML Operations

Supports DML/DDL operations, such as Insert, Update, Select, Delete, Create or Drop.

Integration Methods

  • Append

  • Incremental Update

Load Methods

  • Generic Load

  • Oracle SQL*Loader

  • External tables

  • Database Link (Oracle to Oracle)

Staging Methods

Can be used as a stage for data transformation, mutualization, and more. The following methods are supported:

  • Staging as Sub-Query

  • Staging as View

  • Staging as Table

Rejects

Supports defining Reject rules to detect or filter out specific data during integrations.

Replication

Supports replicating data to or from this technology using Replicators.

Slowly Changing Dimension (SCD)

Supports the Slowly Changing Dimension (SCD) feature when integrating data in this technology.

Change Data Capture (CDC)

Supports Change Data Capture (CDC), which allows you to capture, follow, and store all changes made when integrating data.

Sub-metadata support

The Oracle component lets you create Sub-Metadata on Oracle Database schema and query folder Metadata nodes.

To learn more about Sub-Metadata, see Work with Sub-metadata.

Additional features

Feature Description

Table analysis

Analyze work and target tables with ANALYZE TABLE or DBMS_STATS.GATHER_TABLE_STATS to optimize data loading during integrations.
Change Data Capture may depend on your Oracle license. When capturing changes using anything other than the triggers, make sure the license includes rights to use the template features.

Limitations

Max name size

Oracle Database 12c Release 2 (12.2) and later support a maximum name (identifier) size of 128 bytes for table and column names, or 128 characters with single-byte character sets. When reverse engineering or creating tables from mappings, make sure to use names that do not exceed this limit.

Versions of Oracle Database prior to 12.2 support a maximum name size of 30 bytes. If your Oracle metadata objects were created before xDI version 2026.1.1, xDI enforces this limit for compatibility. You can increase the limit to 128 in the metadata object properties, in the Advanced finger tab.

XML type columns

Support for XML type columns requires additional libraries that do not come with Semarchy xDI. You must find and add the following JAR libraries to the Oracle module:

  • orai18n (orai18n-<version>.jar, based on your database version)

  • xdb6.jar

  • xmlparserv2.jar

For instructions on adding libraries to a module, see Review or edit modules.