Welcome Guest! Log in
The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

This article describes the principal changes of Oracle Component.

If you need further information, please consult the full changelog.

Component download section can be found at this page.


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.


This article is dedicated to Stambia DI 2020 (S20.x.x) or higher.



Template INTEGRATION Oracle

The md: paramValue () syntax is used instead of the $ {} $ syntax to evaluate parameters. 


Template - INTEGRATION Oracle to File (Sqlplus)

The template can be used with Transparent Staging Areas


Complete changelog

The complete changelog with the list of improvements and fixed issues can be found at the following location.



New template Integration Oracle to File

A new template Integration has been added allowing to generate a Flat File using SQL*Plus and provides usually better performances than Standard templates.

 oracle to file

This version contains also some fixed issues.

The complete changelog can be found at the following location.



Some fixed issues on Integration template

The complete changelog can be found at the following location.



Addition of datatypes

Some new datatypes have been added, highlighted below:

 oracle datatype



Integer Data Type

The INTEGER datatype was missing in Oracle Metadata product.



Minor improvements and fixed issues

This version contains some minor improvements and fixed issues, which can be found in the complete changelog.

Complete changelog

The complete changelog with the list of improvements and fixed issues can be found at the following location.



INTEGRATION Oracle Template

Two new parameters have been added to define Oracle hints to be added to generated select and update statements:

  • Target Update Hint
  • Target Select Hint


Temporary Objects Storage clause

In Oracle Metadata, two new attributes have been added in the "Temporary Objects" tab on a schema.

They allow to specify additional table storage clauses which will be added to the statements generated for temporary objects.

For Oracle, this allows to define for instance a custom tablespace to be used for the temporary objects.


The new attributes are the following:

  • Default Table Storage Clause
  • Default Index Storage Clause


Example of tablespace definition:



Change Data Capture (CDC)

Multiple improvements have been performed to homogenize the usage of Change Data Capture (CDC) in the various Components.

Parameters have been homogenized, so that all Templates should now have the same CDC Parameters, with the same support of features.

Multiple fixes have also been performed to correct CDC issues. Refer to the changelog for the exact list of changes.


Complete changelog

The complete changelog with the list of improvements and fixed issues can be found at the following location.



JDBC Drivers classes and URLs


  • Stambia DI Designer 2020 (S20.2.0) or higher


Stambia DI Designer 20.2.0 introduces an improvement which allows Components and Modules definition to provide themselves the proper JDBC drivers classes and URLs, for the connection wizard to automatically adapt depending on the Module selected.

This Component has therefore been updated to take into account this improvement and provide the necessary JDBC drivers classes and URLs information.



Sample project

The component example project can now be imported directly in the "New" menu of the Project Explorer.



Maximum VARCHAR2 size

From Oracle V12, the size of VARCHAR2 type fields is no longer limited to 4000 characters.

Define the Oracle Version on your Metadata, in the "database major version".

If this version is less than 12 or empty, the size remains limited to 4000.

If this version is greater than or equal to 12, the size is no longer limited (up to 32,767 characters maximum).



Fix an issue with creation mask for VARCHAR2 and CHAR datatypes

Creation mask for VARCHAR2 and CHAR datatypes should use 'CHAR' as character type when no information is provided.

Now when loading data into Oracle from any source, if there is no character type information defined on the sources Metadata, the columns created using the creation will use "CHAR" as character type instead of specifying an empty value.

For instance: mycolumn VARCHAR2(255 CHAR) instead of mycolumn VARCHAR2(255)


This will make sure the same character type is used when no information is provided instead of relying on the database default value which may vary between databases configuration and which can cause issues.



Suggest a new Article!