Oracle Data Integrator (ODI) Reviews

Our ODI usage is expensive and is mainly for the extraction transformation and loading (ETL) of data from multiple sources to a data warehouse.

The most valuable feature of ODI is the to use of the whole ETL to create a data lake.

We have been using Oracle Data Integrator (ODI) for approximately five years.

At this point in time, we are not satisfied with the stability. However, this is not because of the solution, but because of the deployment which was done in 2017, and the maintenance and upgrades that needed to be done, which were not done over time.

ODI is a scalability solution as long as you are keeping it up to date with all the upgrades and patching, you can scale it a lot.

We have approximately five engineers who direct users of ODI, and there is a great number who use the solution.

We used technical support and they are good.

We did not use a tool prior to ODI.

The initial setup of ODI was straightforward. The full implementation took us approximately two months because of our architecture, it was not the fault of the tool.

We used a third party to do the implementation of ODI.

We have approximately five engineers that do the maintenance and support the solution.

There is a standard license to use the solution but there are other costs in addition, such as hardware and operating system.

I rate the price of ODI a three out of ten.

My advice to other people implementing this solution would be it is good as long as the context of the systems that they are using it. For example, if they are using a lot of Oracle technologies, then it makes sense to have ODI, otherwise, there are other tools that could make more sense.

I rate ODI a seven out of ten.

Integration with all systems is easy with Oracle Data Integrator, and it is easy to use. I have not used any other product, but with Oracle Data Integrator, we can easily connect to an ERP system, an SAP system, or a cloud application.

It has been very good. Just recently, I've faced an issue, but I solved it somehow. While integrating with a file, I faced an issue where I wanted output files, and I had used the text field limited quotations, but at the end of the file, there was a line breakage for the last column. So, we just removed the text field because it was not working correctly for us.

I have been using this solution for around seven years.

It is pretty good.

It is scalable.

I didn't contact them for the line breakage issue, but I have contacted them for other things. My experience with them was good. Their solution was quick and the response was quick. I would rate them a four out of five.

We have seen a return on investment with this product.

Everything is good, and I would rate it an eight out of ten.

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.

I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support.

Oracle Data Integrator (ODI) is already good as a solution. Still, it needs some editing of its preview package, or if the package is upgraded, that will make Oracle Data Integrator (ODI) even better.

I've been using Oracle Data Integrator (ODI) for more than seven years.

Oracle Data Integrator (ODI) is a stable solution.

Oracle Data Integrator (ODI) is a scalable solution.

The technical support for Oracle Data Integrator (ODI) is good. Here in Turkey, you can directly contact support, and the support team is knowledgeable about the solution.

The Oracle Data Integrator (ODI) technical support team is a four for me on a scale of one to five.

The initial setup for Oracle Data Integrator (ODI) is straightforward.

The Oracle Data Integrator (ODI) pricing isn't expensive, but it's not cheap, so it's in the middle. I'd rate the pricing as three out of five.

We evaluated Informatica and Microsoft SSIS.

My advice to anyone looking into using Oracle Data Integrator (ODI) is that it's easy if you have experience with Oracle technologies. Still, if your experience is with other technologies, you may find Oracle Data Integrator (ODI) challenging.

I'd rate Oracle Data Integrator (ODI) as seven out of ten because it's not as user-friendly as Informatica. It's not as cheap as Microsoft SSIS, but it's an Oracle product, and Oracle is well-known, so that you can search for information about Oracle products on Google. You can find support for Oracle products, so Oracle Data Integrator (ODI) is a seven for me.

I'm an Oracle customer.

We had an opportunity to set up a data warehouse. We were doing a complex stack of Oracle. The customer was using Oracle as their backend database.

It can extract all day. It doesn't look after any particular database. It is not platform-dependent, and that's the main thing that makes it really useful.

It has good plug-ins.

The studio was quite useful.

It was a user-friendly product.

The product is stable. It's scalable. 

The price needs to be lowered. It's too expensive. 

There are a few other tools that can do what Oracle does. It's not necessarily the leader in the space. 

As far as what I have learned from other people, I've heard that the Oracle console is big and confusing. If it was less complex, it would be easier to customize.

I've used the solution for two or three projects. I last used it less than a year ago.

This is a very, very stable product. It's reliable. There are no bugs or glitches, and it doesn't crash or freeze. 

The solution can scale well.

I haven't created any tickets through support. However, my understanding is that, once you open a ticket, they will ask many, many questions, and they do resolve things. It can just be frustrating when you need a problem solved, and they just keep asking questions. There's a bit of going back and forth.

We are actually moving away from Oracle, as it's not very reasonable cost-wise.

What you can do on ODI, for example, can be done on SSIS from Microsoft too, which is free of cost.

In terms of the initial setup, at first, it was a bit hard for me. That said, it is pretty straightforward once you are done with this data source connection tool and once you are done with this on the repository side. Setting up a reporting server was easy, however, doing the middleware, especially on the application server, was a bit tedious for me.

I'd rate the setup process a four out of five in terms of ease of implementation.

It's quite an expensive solution. We'd like it if they could adjust the pricing according to the region they are operating in. 

Per user, it is $900 USD per year, though they will give some discount. However, even a 60% to 70% of discount for each won't help us much. On top of that, there is the perpetual license you must pay at the outset.

I'd rate the cost at a one out of five in terms of affordability.

I've used the solution mostly on the testing side. I haven't done anything on the client side or on the production side. 

I'd rate the solution nine out of ten.

We use ODI for integration services from different systems, such as finance systems and online display systems. Additionally, we integrate it with the external partners with ODI. 

We use ODI in combination with the SFTP server.

The most valuable features of ODI are the ease of development, you can have a template, and you can onboard transfer very quickly. There's a lot of knowledge modules available that we can use. If you want to connect, for example, a Sibyl, SQL, Oracle, or different products, we don't have to develop them from scratch. They are available, but if it's not, we can go into the marketplace and see if there's a connector there. Having the connector available reduces the amount of hard work needed. We only have to put the inputs and outputs. In some of the products, we use there is already integration available for ODI, which is helpful.

The interface of ODI could be improved. For example, navigating and finding functions can be difficult. For example, you have to know which step you need to go to look at where your job status is. The logical step is a bit complex compared to other tools. It's much easier to get a graphical view, but with ODI, it's graphical, plus you have to know all the other pieces that fit around it. You have to think about the logical and physical aspects.

One aspect I always struggle with is there's no single view to see which jobs are going to run or what time. You have to look around, it's very clunky. If you had a couple of agents, you can't see everything in one place. You have to go and look at an agent schedule and look at that, and then, go to another one to look. There's no single view that gives you the whole picture.

What would be nice for us is, if ODI can easily integrate to GitHub, to allow us to have all our source code in GitHub rather than within ODI. This would be a very good feature, everyone is using GitHub.

I have been using Oracle Data Integrator (ODI) for approximately two years.

Since we moved to the new version, ODI has been very stable, and we haven't had any unplanned outages. We only have had planned outages, I'm pretty happy with it.

The only issue we have had recently was when we patched ODI all the jobs that were supposed to be scheduled at 6:00, it ran seven hours earlier. It's a result of the patch. We were working with Oracle and they gave us a fix.

The solution is scalable, we can increase the agents and let it do more work.

We have approximately 12 people using the solution in my organization.

We use this solution extensively without our organization.

The technical support is very good. f you give them all the information, they seem to give you a solution pretty quickly. We have not had any issue with the support. However, we are using paid support and I am not sure if the regular support is the same.

I've used other solutions previously, such as Microsoft tools, they are much easier to set up. ODI is a bit clunky to begin operations, it requires a longer learning curve.

We are using this solution extensively.

The initial setup is complex, it took us three months.

We reached out to Oracle and a few other partners that Oracle has but, in the end, we decided we should do it ourselves. If we did not do it ourselves we wouldn't have the knowledge of how to do it in the future. We received a quotation from them and then decided, we would do it ourselves, in-house.

For all these cloud products, we have to patch them ourselves, it is not done automatically. I was expecting patching to be automatic but it is not. 

The solution is expensive because of the model they use. The cost is for the license and for support.

I would recommend it if they were an Oracle house mostly. It works very well with other Oracle products. If a business is not an Oracle shop, I would not recommend it. OBI understands Oracle E-business, Oracle CRM, and other Oracle products well. However, if you were to go to another company that had different products, ODI would struggle.

I rate Oracle Data Integrator an eight out of ten.

We mainly use ODI to integrate all of our EPM applications, which includes Essbase ASO/BSO cubes, Hyperion Planning, DRM and HFM applications. Also it is used to manage a custom data warehouse developed in Oracle DB which is used as source for OBIEE reporting.

We use ODI to integrate all Oracle EPM suite used in our financial area. ODI is the core engine used to move data across different applications every day. It’s by far the most important architectural element in our BI/EPM environment since all data passes through it.

ODI has the ability to connect to virtually any technology out there. If it does not connect out-of-the-box, we can very easily add a new technology into it. This flexibility gives a tremendous developmental advantage to its users, which can use ODI as the official ETL tool for any kind of integration project.

Its Knowledge Modules (KMs) may abstract the “how” portion of integrations, allowing the users to focus on the “what” that needs to be done. It can be easily used by either young ETL developers or expert professionals.

For resumes, the ease of use for young professionals and its great development flexibility for expert professionals make it a great product to be used for every ETL project out there.

In my opinion, ODI should connect to ALL Oracle products out-of-the-box, but currently that’s not the case for all of them. Hyperion Financial Management (HFM) is one of the Oracle products for which Oracle decided to remove its ODI support in its last product version. In other words, if you wish to use ODI and HFM together, both from Oracle, you will need to create custom code, which does not make any sense to me.

Another area to improve would be the development life-cycle, which did improve in the latest ODI version, but needs further improvements.

More than five years.

ODI 12 version is very stable. It can manage several parallel executions/large volumes without much trouble.

ODI scales very well.

This is a delicate subject. My experience with Oracle support has both great and very bad situations. If the problem that you are facing is only related to ODI, then your chances of having a great Oracle support experience are good. But if your problem involves multiple technologies, like ODI integrating EPM apps, then it is probably going to be a nightmare (and, unfortunately, most of the problems that will require support assistance will involve “multiple technologies”).

This happens because Oracle supports different technologies with different teams and the communication between them seems complicated sometimes. Several times I was in a situation where teams would keep discussing who should fix the problem instead of actually fixing it.

I've always worked with ODI for ETL development.

The initial setup is extremely easy and straightforward.

ODI was the only option we considered.

Our main use case is getting data from operational systems. We are integrators and implement this solution for our customers. I'm the company's director of analytics.

This is a stable and comprehensive solution. 

The initial setup could be easier and it would be helpful if they'd reduce licensing costs.

I've been using this solution for more than 10 years.

The solution is stable. 

The solution is scalable. 

Customer service is reasonable. 

The initial setup is not that straightforward, you have to know how it works to deploy and implementation takes several months. We use managers or admins for deployment. 

We pay an annual license fee and this product is more expensive than other solutions on the market. 

I rate this solution eight out of 10.