Welcome Guest! Log in


Stambia Data Integration allows to work with Oracle databases to produce fully customized Integration Processes.

The database structure can be entirely reversed in Metadata and then used in Mappings and Processes to design and adapt the business rules to meet the user's requirements.

Prerequisites:
  • The Oracle JDBC driver must be installed in the Designer and Runtime
  • If using SQL*Loader, an Oracle client must be installed on the machine where the Runtime is located

Note:

Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

 

Download

You can find below the necessary material to work with Oracle in Stambia DI

Name Description Download 
Generic Templates Package containing the generic Templates download
Specific Templates

The Oracle specificities are handled in dedicated Templates that can be found in this package

Some are using generic tools that are shipped with the generic templates, make sure to import them too.

download
CDC Templates Package containing the CDC Templates download
Demonstration Project

A Project that demonstrates most of the features through examples of Processes and Mappings.

Note: The examples have been developed with the S18.3.2 Designer version, that is so the minimal recommanded version to use to import the Project.
download

 

Supported features

You can find below an overview of what Stambia DI can do with Oracle databases

Standard features

Name Description
Reverse

The database structure can be reversed in a dedicated Metadata

DDL /DML Operations

 

DML/DDL operations can be performed on the database, such as: Insert, Update, Select, Delete, Create or Drop

Integration methods
  • Append
  • Incremental Update
Staging

The databases can be used as a staging area to make data transformation, mutualization, ...

The following modes are supported:

  • staging as subquery
  • staging as view
  • staging as table
Reject

Reject rules can be defined to filter or detect data that does not fulfill the rules during integrations.

  • Three type of rules can be created: Fatal, Warning, Reject
  • Depending on the specified type, the rejected data will not be handle the same way
  • Rejects of previous executions can also be recycled
Replication

Replication of databases is supported.

The replication source can be any rdbms, Flat files or XML files.

 

Advanced features

Name Description

Slowly Changing Dimension Integrations

Integrations can be performed using Slowly Changing Dimension (SCD)
Load methods
  • Generic load
  • SQL*Loader
  • External tables
  • Database Link (Oracle to Oracle)
Analyze of tables The work and/or target table can be analyzed with ANALYZE TABLE or DBMS_STATS.GATHER_TABLE_STATS to optimize data loading during integrations
Change Data Capture The Change Data Capture (CDC) allows to follow and store all the changes on the tables

 

 

You have no rights to post comments

Articles

Suggest a new Article!