Oracle Data Integrator (ODI) Reviews

The EL-T approach that will first load into the target dataserver before doing the transfer is a great architecture improvement compared to standard ETL tools that use a staging area and usually process the data in Java. With ODI, almost all the job is pushed down on the underlying technology, for instance the Oracle database or the Spark server.

The Knowledge Module approach provides an easy and reusable way to create our own integration strategies. It's easy to create these Knowledge Modules to connect to new technologies, for instance.

ODI is really the tool for any kind of integration because it speaks the language of the technology we connect. We can work with RDBMS but also in Hadoop, cloud services, flat files, web services, etc.

Thanks to the flexbility of the tool, we could build 3 mappings using variables and the substitution API in replacement of 300 mappings in Oracle Warehouse Builder. It's much easier to maintain!

- Development Lifecycle

- native REST integration

- Easier security

5 years

A bit unstable and buggy in the 12.1.2 release, but most of it is fixed in 12.1.3, so I would definitely recommend to jump to that version.

I used Oracle Warehouse Builder (OWB) which is now at the end of its life. ODI is much more flexible and has the great advantage to be able to connect to a lot of different source or target technologies.

It was quite straightfoward.

We did a migration for Oracle Warehouse Builder to Oracle Data Integrator 12c using the migration tool provided by Oracle. And I've to say I'm surprised to see a migration tool working so well!

In-house

Heterogeneous technologies can be integrated with ODI, including the latest web services.

I feel that Oracle provides users with the best functionalities from ODI by constantly improving the functionalities in all areas.

Any IT company that relies on data coming from its clients or internal users requires data maintenance. All that collected data should be able to provide insight into the various behaviors of the clients across different platforms. For us, ODI has been key in collecting, transforming, and storing information from our various sources.

The two areas that I see for improvement would be the UI and the procedures for accessing it.

I have been using ODI for the last seven years starting with 10g. In my experience, Oracle has spent a lot of effort in improving the tool.

I never faced issues with the deployment since 11g. Oracle has made very good improvements in terms of the deployment. DBA objects take more time than the code deployment, which are the easiest and quickest ones. There is no room for errors when we have an environment in production.

We have had no issues with the stability.

There have been no issues scaling it.

5/10 - Technical support needs to be improved.

I haven't used any other solutions since this product has the potential to provide a solution for any complex requirement.

It's straightforward to set up.

We implemented it through a vendor.

I definitely recommend using this for any data warehouse project.

It's highly flexible, and can interface with almost any technology. One of the best ETL tools.

It has streamlined and automated data loads, and exports from our ERP system to our finance data warehouse and to Hyperion Essbase. The post-data load tie-back to the source system was also performed using this tool. The tool has also made metadata management more efficient, and automated the process from relational source to Hyperion Essbase.

I've used it for four years.

No issues encountered.

It used to crash with large datasets.

I've never had to contact them.

This is the only ETL tool I have used and never found a need to look for another. It met all our needs.

Straighforward except for DBA involvement during installation for schema creation.

The implementation was done in-house.

It's a great product.

I'm a technical manager and we provide technical services to our customers. We are partners with Oracle. 

This product helps our customers achieve their goals and objectives.

The best feature of this solution is the documentation. Everything is set out clearly with step-by-step instructions.  

I think Oracle should add more functions to improve optimization. Automation should be improved to enhance the product. Some of our customers carry out data comparisons between Oracle and other features and Oracle is lacking in some of those tools and features.

The stability and performance are good and our customers use the solution on a daily basis. 

The scalability is good, we have around 100 users. 

The initial setup really depends on the situation so it can sometimes be more complicated. When it comes to implementation, a deployment will usually take around 40 days and up to six engineers. 

I rate this solution seven out of 10. 

Our primary use for this solution is a data integration and merging tool. It easily connects to many databases like MySql, SQL Server, etc. It's completely user-friendly. We can easily manage packages, ETL, and Procedures.

Before adopting this solution we used to work hard. We now feel better because our manual work is completely over. 

We can easily create ETL processes and schedules. We can check logs on a daily basis. It handles multiple routines very smartly.

Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts.

My impressions are good in terms of the stability.

I find that the scalability of this solution is good.

Interaction with technical support is not my area.

Before this solution, we were using SQL Server.

I think that the initial setup is amazing.

We used a completely internal team to implement this solution. 

We found that the cost compared to other integration tools is a little high, but the solution works great.

We evaluated SQL Server prior to choosing this solution.

We use ODI to integrate data from the OLTP database to the data warehouse. The source database systems including Oracle, MySQL, flat files... Our business background is OTA and the total data is about 100T.

In our DW/BI solution, ODI is the main tool to integrate the data as a daily batch. Besides loading data, we do most of our transformations in ODI. ODI is quick to use.

Most of the functions are very straightforward, like the data model, mapping, package, and load plan. Thus, a new user could get started very fast. 

The ODI scheduler for agent sometime fails with no sign, which impact the ETL solution severely.

The property window in the ODI studio always does not refresh as it should. 

Sometimes, the mapping or package automatically gets edited.

The stability of the ODI studio is not strong enough. It crashes occasionally. 

Informatica and SSIS are also good ETL tools besides ODI.

The installation of the client tool: ODI studio is easy.

Basically the ETL tools is determined by the database.

It is a clever integration tool to extract data from every possible source, and it can transform the source data to a format the targets can handle. It is suitable for data warehouses and data migrations.

We replaced many manual actions and tasks with mappings in Oracle Data Integrator, and created schedules, and then used SOA Suite services to automatically transfer large data amounts between different systems.

The integration between the Oracle Repository and versioning tools like TortoiseSVN.

We’ve used 11G for four years, and 12.1.3 for two years.

One of the benefits of it is the usage of the principle ‘write once, execute anywhere’. You set up the architecture in the topology within Oracle Data Integrator.

We've experienced no issues with performance.

We haven't needed to scale it yet.

We haven't needed to use it yet.

Previously we used Oracle Warehouse builder, and custom made PL/SQL data warehouses. We’ve chosen Oracle Data integrator over other solutions because it is the successor of Oracle Warehouse builder, and Oracle Data Integrator provides a more structured working-method, and the data warehouse is easier to maintain.

The installation is rather straightforward, with the available documentation it must be possible to do the installation by yourself. You must have sufficient knowledge of Oracle Data Integrator to make the correct decisions during the creation of the architectural setup.

We used an in-house team but hired interim experts, and created a team with combined knowledge levels, from rooky to expert. The initial setup is rather complex, and needs an experienced architect to make the correct decisions. The change of success is highly depending on the decisions that are made during the setup.

I have no info on the ROI or the licensing, but I know the license costs are high, so Oracle Data Integrator is only suitable for the larger companies.

To benefit the most of Oracle Data Integrator it is important to assemble a team with the experience to make the project a success.