Oracle Data Integrator (ODI) Reviews

We use the solution for getting transactions and BI reports for stakeholders.

Stability could be improved because some operators have issues.

I have been using Oracle Data Integrator for two years and a half.

We used the solution, and we didn't have any problems with that.

I rate the solution’s stability a six out of ten.

We didn't have a problem with the tool’s scalability. There are six to seven people using this tool in our organization. We don't have plans to increase the usage. It responds to all our problems.

We didn’t contact the customer support team. We figure it out by ourselves.

The initial setup is easy. It took about two and a half months to deploy.

We set up the tool in an environment because of data sensitivity.

Overall, I rate the solution a seven out of ten.

The most common use of this solution is to connect to the database source and database target. Data in the repository constructs the mapping or programs to form the data into the target using the CAEM knowledge model. I'm a data warehouse analyst. 

The CAEM is very useful, particularly in its modularity and portability. We can also use real-time transformation to build and load data. It works more quickly than other ELTs and it's very simple and modular. It can be used for all integrations, not only AIT or ELT.

Reverse engineering is complicated when reversing from the database to the repository. It's pretty challenging to manage.

I've been using this solution for four years. 

The solution is stable. 

The solution is scalable.

To date, we haven't needed customer support. 

The initial deployment is very simple and we carried out the implementation in-house.

I rate this solution nine out of 10. 

We have been using Oracle Data Integrator for populating Financial Services Data Warehouse. Data extraction is done into a staging area from different source systems and then this data is validated and certain quality checks have been performed here. We used Oracle Data Integrator data quality checks builtin capability to perform these different data quality checks. Then data is consolidated and transformed into the staging area and finally gets landed into the data warehouse. I also used this for generating data hand-offs for other applications.

Oracle Data Integrator offers a declarative style ETL development, where you mainly use pre-built knowledge modules for doing integration tasks. As a developer, you don't need to focus on how part of the integration, you only focus on what to do. You just need to configure certain components as per your requirements and underlying execution plan and code is generated for you. For every technology there are knowledge modules available, the best optimal code is generated which eventually gets executed on database level. Our developers created best performing ETLs with very little effort leveraging this feature.

There are number of valuable features in this tool: 

• Declarative design 
• Client-server architecture model.
• Very good user access model
• Pre-built user profiles defined that give you control for access management
• Very good logging and execution logs feature which gives you complete detail of executions and you can query these in a different manner.

All ETL code is stored in repositories in underlying database schemas. The number of users can access and work on the same solution using a client tool. So distributed teams can work on this tool in an efficient manner. 

There are certain things where it can be improved. Initial solution setup seems a bit complex at the start, it should be improved because it becomes bit tough for a novice to get started on this. Sometimes error description is not helpful to understand the problem it gives some generic type of errors which are at times not that helpful to understand the underlying root cause of the issue. 

Error descriptions should be easy and specific to actual problems rather than generic lengthy descriptions. Also, another main feature that should be readily available is that there should be a source component available that can extract data from a source based on the custom query rather than giving a source data store only in the mapping. 

I have been using Oracle Data Integrator for five years. 

Good.

It's very good.

Whenever we needed Oracle Technical Support, we're able to get it in timely fashion and most of the time has been good to help in resolving the problems.

I didn't switch any tool. I'm a professional developer and my tool selection is based on client requirements. I've used both SSIS and ODI for different clients.

The initial setup is a bit complex as it needs some repo schema setup and agent setup.

We did it at our own.

Excellent.

ODI has bit on higher end in setup and pricing but it has more power as well. So it depends on your use. 

No, my selection was based on client's choice.

I think different tools have their own pros and cons, so it all depends on your overall needs.

The biggest feature for ODI is the fact that it uses the power of the source or target database to actually perform the ETL processing. So a typical data integration tool might have its own ETL engine, and that would be an additional server, additional costs, something else you have to maintain. ODI actually has the ability to create and generate code that runs potentially on your Oracle database, or even on a big data target, on Hadoop or somewhere like that. So, you have that flexibility, and you don't have to have that additional cost in maintenance.

A couple other additional benefits of Oracle Data Integrator would be the use of what's called a knowledge module. So this is like a code template that uses the metadata that you have available within ODI, and within your mapping, to generate that code, that then can be executed, like I said before, on the source or target system. The code will be generated in the native format of that database or that technology. So, again, you have sort of a hands-off.

These knowledge modules are built in. They can be developed and modified. So, the biggest thing, I always think, with ODI is, it fits around your data warehouse needs. Rather than taking your production, or your business, and trying to make it fit a tool, you do the opposite. You make the tool fit your business.

One thing that is included, and it's going to improve, is the integration with a configuration management tool. Right now, they integrate with Subversion. And we know in the future, there's going to be more tools implemented there for configuration management and some new features there. So right now, it's kind of one of those features that, it's been released, but it's sort of a beta version of that feature where a lot more functionality will be coming down the line.

So ODI is actually quite a stable product. As a testament to the product team that develops it, they're not going to release something that is extremely buggy or things like that. So, I do see that often they will release features that are highly anticipated and highly sought after. And they might release them a little early. So there's definitely patching that comes into play there, to kind of get the full solution there.

As far as stability, the Oracle Data Integrator has agents that run either in WebLogic, as a Java deployment there, or on a server as a Java agent, or a Java deployment. As long as a client has had the product implemented, with no issues there. So that's kind of the key there, you don't want to have those agents have a blip or any issues.

So as far as scalability of Oracle Data Integrator, from the high availability standpoint, if you use WebLogic for your agent, you can use the clustering capability within WebLogic to create multiple nodes on different WebLogic servers. And then run your agent through that process there. So if something fails, if the main agent fails, it can fail over to the secondary agent or, again, another agent in your cluster.

I'd probably put them up there around an eight, yeah. Being a system integrator of Oracle products, typically I'm on behalf of a client. So oftentimes it depends on who your client is and what their level of support is, as far as response and how things go. But I've always had great response with those guys.

A lot of the projects I've worked on recently are Oracle VM apps projects. So, it's the folks that are in the Informatica version of VI apps, and looking at moving to the latest and greatest, which has Oracle Data Integrator behind the scenes. I'm not saying they're actually talking about using Informatica, they're just, that's what they have. And they're looking to migrate. Quite often where we come into play, ODI is typically chosen at that point. And then they call us in to help with it.

It's not too difficult. It's tough to look at it from the perspective of someone who hasn't been doing it for a while. And oftentimes, that's what you need to kind of make that determination. But as far as just getting up and running, you can get it installed, configure an agent, quite quickly. And then the next step would really be getting ready to build a mapping. And they actually introduced in the most recent release, or maybe even when 12C came out, they introduced a feature that would basically get everything, topology, the models, all the data stores, everything, ready to go for you, just in one simple wizard. And then you could actually start building mappings quickly.

A lot of it is when they have home-grown ETL processes. So they'll manually script their ETL code. It's basically something that's difficult to maintain. So we talk about how we can use ODI to keep everything centralized. And even if we're not using ODI to actually build out mappings within the product, we might still be able to run that PL SQL or whatever it is, the script for ETL, from within ODI.

So we still have everything consolidated and contained and then the other approach, or reason for moving to ODI, would be the need to get off of that middle tier integration server. That we don't need with ODI.

As far as why consider Oracle Data Integrator, I think the big thing is the ability to consolidate all of your ETL into one place. Whether it's an Oracle to Oracle, source to target load, or even Oracle to Hadoop, or anything in between. SQL Server, MySQL, XML. ODI can basically talk to all of those different technologies. From a consolidation of all of your data warehouse or your data integration, if you will. And also, just use the same approach for mapping and creating processes for all of those different types of solutions. You have everything logically defined. And so when you're developing, it actually doesn't look any different than an Oracle source, and target doesn't look any different than a Hadoop source and target.

So I would rate ODI a nine. And that's really because, just looking across the other ETL tools, so I mentioned Informatica, there's a lot of other ones out there. I've seen what ODI does from a sort of a declarative design approach, and the push-down of work to the source and target. I've seen that replicated in other tools that have come out after Oracle Data Integrator. That's a big key.

It puts it kind of at the top, if you're going to look at a scale across all of the ETL tools. The other aspect to that rating is how they're integrating a lot of the big data technologies now. And it's a big deal from an Oracle standpoint, it's kind of how things are going. And it also just makes sense to, again, keep everything consolidated in one place. You already have an investment in ODI, it makes sense to try to drive some of your other big data type Hadoop loads or whatever it may be from that same place.

ODI is integrated with Hyperion Planning, Essbase and other Oracle products. Data transfer is also easy since ODI already knows the metadata of these applications between the different databases. There is also ease of development in terms of the interface and customization with scripts, as well as data lineage and tracking, which are advantages to us.

We hadn’t upgraded in a long time, so all of our business users were creating their own solutions with spreadsheets, for example. We realized we were behind and purchased a whole stack of Oracle products that have simplified the way we move and track data. The accountants enjoy being able to reconcile where the data is and how it is changing. That’s the reason we bought the tool.

It would be nice to improve reconciliation. Additionally, better external authentication support through Microsoft Active Directory would be useful. Right now, it doesn’t support this very well. You have to buy Oracle’s special product instead.

When you start integrating products, it's not that stable. For example, if you upgrade other applications, like Hyperion Planning, it's going to break ODI.

I still need to learn a bit more about scalability in ODI, but I don't think you can scale it like DataStage.

Technical support for ODI has been awful, but I think it differs by product because support for OFSAA is wonderful. When I gave tech support a problem, the answer I got was “Oh. Well, keep testing.”

Initial setup for version 11.1.1.7 of ODI was a little difficult, but installing 12c was really easy.

I haven’t checkout out other solutions, so I don’t know where it scales, but from a developer’s standpoint, I’d give the product a seven or an eight. On infrastructure, I’d bring it down to a five.

The main features we use and has helped us to implement our ETL process are

• Data transformation
• In memory engine
• KM customization
• User friendly GUI
• Versioning
• Big Data support
• Security support
• Easy deployment
• Reusable Mapping
• Multiple Target Load
• ELT Architecture
• Application Server support for other vendor servers such as IBM Websphere

The features that we have applied to our project has helped us reduce manual effort and increased our scalability and growth. I worked on multiple domains where requirements were adversely different. We used many ODI features to enhanced our data transformation capability.

I am personally satisfied with current version, however, I think they should be able to provide a feature where we can easily use a configuration tool for TFS, GIT etc. This is essential for code management.

I've been using it for six years.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

9/10

8/10

I have not used any other product. However, I have seen other ETL tools in use such as BODS, SOA, and Informatica and I did not like them as I did not that they were user friendly.

It was straightforward. I used an application server for the initial setup and I did not find any challenges.

We performed an in-house one. If you have a technical team for ODI, then they can easily perform any implementation. If not, then you should have the vendor perform your implementation.

10/10

It is not as costly as other ETL tools.

You should use Oracle Data Integrator for your data transformation, or at the very least give it a try.

We primarily use the solution for digital health and sometimes automation tasks.

The integration of the solution with Oracle is very good. It's nice and easy.

The scalability is great. It's one of the reasons we chose the solution.

The stability is okay.

We found the implementation to be quick and easy.

The resource management aspect of the solution could be improved.

The migration process could be easier.

Technical support could be better. They're okay, however, their service could improve a bit.

The solution could be more reliable.

I've been dealing with the solution for around four years at this point.

The stability of the solution is pretty good. It doesn't crash or freeze on us. We don't have any bugs or glitches. 

We have about 20 people using the solution within our organization. They use it on a daily basis.

We deployed with scalability in mind. We've found it to be quite effective.

We've contacted technical support in the past. They're okay in terms of the service we provide. I would rate them seven out of ten overall. They could be a bit better.

We did previously use a variety of different solutions. So far, this product has been the best option for our organization. It has more features and integration capabilities. It's a bit more complex than other options.

The initial setup of the solution is not complex. It's very straightforward. We found it to be easy.

For simple mapping, deployment only takes about half an hour.

We handle the maintenance ourselves. Occasionally, we may reach out to Oracle for certain tasks, however, largely, we deal with everything maintenance related internally.

We did not need the help of a vendor or integrator. We did do everything on our own.

The solution isn't the most expensive, nor is it the cheapest option. In terms of pricing, it sits somewhere in the middle. Everything is covered under one license. You don't have to buy any add-ons.

We're simply an Oracle customer. We don't have a business relationship with the company.

There's no specific version of the solution that we use.

I wouldn't recommend any other services above Oracle.

Overall, I would rate the solution eight out of ten.

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