Oracle Data Integrator (ODI) Reviews

An area for improvement would be the lack of SQL compatibility - ODI has no ability to interact with SQL unstructured types and data types.

ODI is a proven product with high performance in large-scale data processing.

ODI comes included when buying the cloud version of the Oracle database license.

ODI is very friendly to those who have been traditionally writing a scale PL/SQL. It has lots of connectors to many different sources, although the target databases it supports are relatively limited compared to Informatica. It's also easier to understand, very developer-friendly, and has a big forum community and lots of documentation for support. I would rate it as nine out of ten.

I have found most of the Oracle Fusion middleware and hardware to be valuable.

We are Oracle partners. We have our clients and they need this solution. We implement it according to the clients' requirements.

I think that the Oracle Fusion Middleware stack could be improved.

I have used it for almost ten years.

I had some deployment issues. Sometimes, issues will be erased if the OS and the system do not meet the system requirements and prerequisites before deploying a specific application.

I did not encounter any stability issues.

I did not encounter any scalability issues.

I would give technical support a rating of 10/10.

We have always used Oracle because we are Oracle partners.

The initial setup was straightforward.

I performed the implementation. If there was something that I was unsure about, I contacted the support team for clarifications and update patches. Overall, it depends on the situation and the time frame.

I have seen a decent ROI for the Oracle and Veritas Backup Exec products.

We looked at alternatives, but they could not provide us with the complete set of features.

This is a good solution if they are trying to move to fusion stack.

ODI is a very accessible tool, especially since the mapping functionality has been added.

We added DevOps to ODI.

You can use the ODI versioning or our component, and complement both with lifecycle management, fully-automated deploy and integration with issue tracking.

Three years.

Not with ODI itself, but with deploying programs written in ODI. That is why we developed our solution.

No issues.

No issues.

It could be better.

It could be better.

OWB: We switched because the this tool was at the end of its life.

It was straightforward.

It was implemented in-house by experts.

Not applicable.

It is OK.

No.

It is a great tool to work with.

The ability to build integrations that process large amounts of data (in GBs), be it file transfers ,DB operations, and web service calls, etc.

ODI has made it possible for our organization to rapidly build robust integrations that process large data. The learning curve of this technology is also very smooth and can be picked up by any one with minimal programming experience.

ODI's "in-memory RDBMS" is still a black box for programmers as there are no tools/dashboards to monitor/administrate this in-memory database. As a result, inconsistent data processing issues generally force us to restart the ODI server.

There were no issues with the deployment.

We've experienced no issues with performance.

It's been able to scale for our needs.

The product may not be as evolved as Informatica, but still has a lot to offer in the Fusion Middleware Product Suite. Keeps all the promises of an ETL/ELT tool, but when it comes to Administration and maintenance the product still leaves a lot to be desired.

To have a common ETL tool in the DW team, start a common way of ETL development, set up a process registry, and daily process flow.

• It increased ETL development efficiency 1/3 in time.
• It has a short learning curve for newcomers, compared to previous MS DTS packages and scripting.

• Reusing existing ETL development pattern in the next similar tasks.
• It's flexible to add new common procedures.
• Knowledge modules can be modified to fix small issues.

• ETL process registry solution is missing.
• To manage dependencies between loading packages.
• Versioning logic and release process are not well supported.

We are moving data from everywhere to everywhere else all the time. We will be moving data to a cloud solution in the future and ODI seems to be able to do it as well.

The tool is declarative, and it only runs on the target staging databases, so I have full control over it and I can change the SQL that the tool generates. I do not have to maintain a separate ETL instance. I can change the SQL when something is not performing correctly.

It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases. Going forward, that is very important.

When I do a BI type of project, I like to pick the simplest declarative solution that I can find. So ODI appeals to me at a base solution level, but that sometimes puts a lot of burden on me personally to fix all of the nuances of the platform that I am integrating to and from. Some might argue this is just a part of the job, but if there is an add-on tool to hide the performance issues and solve them for me, then I might be interested in that as it provides me value. I can see a great deal of value of ODI plus an add-on solution that might know how to avoid performance issues on the target database with, for example, the proper use of SQL functions.

The possibilities provided by using knowledge modules and the integration with other Oracle products.

The old fashion PL/SQL codes have been translated into ODI, improving the way of maintenance. Several developers can work on the same project easily.

The software is developed on Java so it is very hardware dependent. You will need enough hardware to run the software otherwise you will struggle with it.

I've been using it for the last four years.

There were no issues with the deployment.

When developing on huge internal repositories, the performance is often quite poor.

It's been able to scale for our needs.

I have managed to solve my questions/issues via OTN or forums.

I haven't used any other products.

The first time might look a bit complex but using the right documentation it should be easy to handle.

It was already implemented on the projects where I have worked.

I didn't look at any other similar products.

Strong and reliable ETL tool with high performance and helpful features

Enhance export/import features and add more features (I think they enhanced it in the 12c version)

More than 3 years 11g and now start working with 12c.

Export/import isn't stable and they don't have a clear behavior.

No issues.

Developed a project on SSIS (SQLServer Integration Services), and used to write ETL in scripts (PL/SQL).

Straightforward set-up.

Go ahead it is a very good, stable and reliable product.