Oracle Data Integrator (ODI) Reviews

We use the product to extract data from various sources like EBS and Fusion, transform it, and load it into data warehousing systems supporting Azure, Salesforce, and KPIs.

ODI has robust ETL capabilities, particularly in its latest version. It introduced user-friendly features like drag-and-drop functionality and improved support for incremental loading, enhancing efficiency and flexibility in data integration tasks.

There could be better compatibility with other ETL tools and cloud platforms, like Azure Data Factory, ensuring seamless integration across diverse data sources and simplifying tasks such as data extraction from Excel, which currently poses challenges.

I've been utilizing Oracle Data Integrator (ODI) since 2016, primarily for ETL purposes.

While recent experiences with Oracle Cloud Analytics were positive, support for ODI-related issues in the past has sometimes been slow, impacting timely issue resolution.

The initial setup process can be complex for new users due to tasks like configuring master and work repositories. 

The platform has significantly reduced the time and effort spent on custom ETL solutions. Its automation and efficiency have translated into tangible savings in time and operational costs.

The product's knowledge module features, such as LKM (Load Knowledge Module) and IKM (Integration Knowledge Module), play a pivotal role. These modules streamline the extraction from source to staging and then to target systems, each serving specific needs like data security and integrity checks.

It effectively manages errors through its logging and exception-handling capabilities. It allows for setting constraints within mappings and notifies users of failures promptly, enabling proactive resolution of issues during data integration processes.

I would rate Oracle ODI a seven. 

We primarily use it as a data platform for all three layers of the architecture. 

The tool improved our data integration workflow primarily due to its compatibility with Oracle. Its integration makes it very convenient for analytics. Its most valuable feature is robust extended capability. The solution's debugging capabilities are good. 

The tool should improve its pricing. It prevents the application of Oracle ODI on small and medium projects in countries like Croatia, Germany, or the US. While there are no technological obstacles to using it, the high price makes it unfeasible for projects with smaller budgets.

I've been working with Oracle ODI for about two or three months. However, I have experience with relational databases, although I haven't worked with Oracle ODI for quite some time. Recently, I returned to it for a data migration project, and I was surprised by its capabilities.

Oracle ODI is stable. 

I'm not directly dealing with end users as we specialize in IT engineering and data management. Our implementation is for a public organization with a few thousand employees. In such environments, various user profiles exist, including occasional users, heavy transactional users, etc.

The tool's support is fine. 

The setup is straightforward but designed for professional use rather than beginners. It's at a normal level of complexity for such a product.

I rate the overall solution a ten out of ten. I recommend it to anyone who has money. While the initial setup may require a modest investment, achieving optimal performance requires high proficiency in technical details. It's unsuitable for beginners and may even be challenging for those with medium-level experience.

Flexibility, ease of customization, extensive features, ease of deployment, and the ability to access to all kinds of different source system technologies. No need for extra hardware for transformation step. Easy to learn & develop.

Now, ODI has Cloud Service which you can deploy your repositories to Oracle Data Integrator Cloud Service for you to use both on prem, Big Data and cloud environments.

Oracle Data Integrator (ODI) can support any type of databases that has a jdbc driver in a native way. I have accessed and retrieve data from an Ingress database. Big data connectors are implemented to ODI 11.1.1.7 (out-of-the-box) and upper version that support many well-known Big Data architecture.

Knowledge Module architecture helps you to build your data integration activities with less effort.

You can switch to source, staging area or target to improve your querying performance. If you have to do a join from different source systems, you can decide which data to move to where and figure out the place for best output.

Variables can help you to perform loops and conditional statements in packages for helping ETL

It helped me to reduce a slowly changing dimensions type 2 with the same output, from 22,000 seconds to 168 seconds.

Loaded 10.000+ files to a table from 1000+ different sources under 20 minutes with approximate 300GB of data per day.

They need to work on the multiuser development environment and include the ability to comply with different kinds of SDLCs.

I've been using it for more than 10 years, since Oracle acquired Sunopsis.

There were no issues with the deployment.

I've experienced no issues with performance. Since sky is the limit, you can do what you want to do within ODI in several ways.

It's been able to scale for our needs. ODI will fit your needs.

10. I generally create a service request per year and they are being solved within a week.

They're very efficient.

We switched because of ODIs impressive increasement in development productivity.

It was straightforward and very easy. Almost the same as setup>next> next>next.

In-house.

Worth every penny.

There are various options in licensing, either per seat or per target core count. It depends how you want to use it.

We also looked at Informatica Power Center, AbInitio, Business Objects Data Integrator (BODI), and SQL Server Integration Services (SSIS).

If you want a robust, flexible solution with no extra hardware that is easy to learn, then ODI is the right product for you. ODI is a tool, that can talk or learn how to talk, with any database or operating system in its own language. This is the power of ODI.

We are using the solution for ETL purposes for our data warehouse.

The product has an ELT approach. It is much faster than any other ETL.

The initial setup is a bit complex compared to other tools.

I have been using the solution for three to four years.

The tool’s stability is good. I rate the stability an eight out of ten. We need to do a lot of engineering to understand the ODI mappings, knowledge modules, and how to load them. We need to learn a lot of other things, too.

It is a native tool of Oracle. It has no problems with scalability and availability. We have around 12 to 14 users.

The support depends on the severity of the tickets raised. A P1 ticket might be resolved fast. P2 or P3 tickets take a long time. I rate the support for P1 an eight out of ten, but for P2 and P3 tickets, I rate support a five out of ten.

Positive

The deployment takes at least 30 minutes. The tool has a lot of prerequisites. If we don't have a consultant or expert to help with the deployment, we won’t be able to complete it within 30 minutes. It would take longer. We must install JDK and the OBIEE repository that contains ODI packets. The software setup is confusing. The installation can be done in-house if the SOP is clear with the prerequisites and steps to follow.

The solution is very expensive. If it is cheaper, more people can use it. Oracle licensing is complex to understand. We pay a yearly licensing fee.

Since the product is expensive, we are exploring other tools like Azure Data Factory to reduce costs.

People can use the tool if they don't have a limit on their budget. However, people generally have budget constraints. We need to understand the cost before we implement the product. Overall, I rate the solution a six out of ten.

I primarily use ODI as a tool for data integration and data warehousing.

ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules.

I've been using ODI for four years.

ODI is very stable.

ODI is scalable, depending on the architecture you use.

Oracle's technical support is pretty quick to respond, but it has several levels, so it can take some time for more complex problems to be solved. 

The initial setup is complex, especially if you also have to install a console. Deployment takes a day or two. 

We used an integrator.

I would give ODI a rating of nine out of ten.

We use the product to transfer data from one stage to another of the data layers. It helps move data from different layers, transform, manage, and put the proper timestamp on the managed data.

One significant area for improvement in legacy ETL products such as ODI and PowerCenter is the steep learning curve and the necessity for a highly skilled development team. We are trying to escape this to provide solutions to end customers more efficiently.

We have been using Oracle Data Integrator (ODI) for over ten years.

I rate the product stability as ten out of ten.

Given the new technologies and complexity, I rate the platform's scalability a five out of ten.

Oracle support services are not up to the mark.

Negative

We are working with PowerCenter from Informatica and StreamSets from SoftwareAG, now an IBM product. We also use Microsoft SSIS in some basic ways.

We have deployed ODI mainly on-premises, accessing some Oracle cloud databases through a VPN. We maintain and upgrade it.

I rate the platform pricing as five out of ten.

We have not evaluated any other product before, as ODI was already in place due to the project's age. We are now evaluating StreamSets to improve user experience and flexibility to scale-up/down according business needs and reduce dependence on highly skilled developers, providing a ready to go solution to functional teams.

The key feature of ODI that makes it most effective for handling large data volumes is its ELT (Extract, Load, Transform) solution. It loads data from the database and then transforms using its resources, which is helpful. It does not require building all the data into the container or the ETL server, which usually consumes more CPU. It uses the power of the database system efficiently.

We are mainly using Oracle products, and it's straightforward. Oracle products integrate very well, reducing the time consumed in transformation compared to other products.

I recommend the product depending on specific business requirements. It can be complex for new cloud integrations and more modern iterations. I don't recommend ODI for those users, especially since it has become a legacy product.

I rate it a six out of ten.

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.