In comparison with other products of the same range, licensing mode is really attractive, no need to license according technology/topology to be used and an incredible Versatility to build any Data type or KM accordingly for proper Data Movement per technology type (Snowflake, Oracle, PostGreSQL, MySQL, Kafka) or Data Movement Strategy (Incremental, Merge, Slow Changing Dimension, Full Load Parallelism).
In addition, it includes a really powerful SDK that allows to programmatically perform any task. I would say that I haven't been able to find any product, that in comparison with ODI provides the flexibility that from Data Movement perspective is required. For its improvement, I would say that it needs to improve the Web based UI without the need of going to a complex Web logic Cluster Deployment on agents.
Learn what your peers think about Oracle Data Integrator (ODI). Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
The solution's initial setup is straightforward, especially compared to Mule, which our team has worked with before and found to be a bit more complex in terms of setup.
The most valuable features of ODI are the knowledge modules, such as the Loading Knowledge module and the Check Knowledge module, they are helpful. We can check for the constraints in ODI. That helps in figuring out what are the constraints that are the primary keys created in the tables. We can check them with the Check Knowledge module.
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.
Applications Support Manager at a marketing services firm with 1,001-5,000 employees
Real User
Nov 18, 2021
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.
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.
Oracle Data Integrator (ODI) is a data integration software solution that provides a unified infrastructure to streamline data and application integration projects. It uses a powerful design approach to data integration, which separates the declarative rules from the implementation details. The solution is based on a unique ELT (Extract Load Transform) architecture, eliminating the need for a standalone ETL server and proprietary engine.
Oracle Data Integrator Features
ODI has many...
In comparison with other products of the same range, licensing mode is really attractive, no need to license according technology/topology to be used and an incredible Versatility to build any Data type or KM accordingly for proper Data Movement per technology type (Snowflake, Oracle, PostGreSQL, MySQL, Kafka) or Data Movement Strategy (Incremental, Merge, Slow Changing Dimension, Full Load Parallelism).
In addition, it includes a really powerful SDK that allows to programmatically perform any task. I would say that I haven't been able to find any product, that in comparison with ODI provides the flexibility that from Data Movement perspective is required. For its improvement, I would say that it needs to improve the Web based UI without the need of going to a complex Web logic Cluster Deployment on agents.
ODI significantly improves data integration and management by allowing customization of data types from various sources like SQL Server databases.
The most valuable feature is Data movement.
The product has an ELT approach.
The initial setup is easy.
One of the standout features of ODI is its ability to prepare everything on a vertical level and create reusable components, which adds to its value.
The solution's initial setup is straightforward, especially compared to Mule, which our team has worked with before and found to be a bit more complex in terms of setup.
The CAEM is very useful in its modularity and portability.
I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support.
What I found most valuable in Oracle Data Integrator (ODI) is that it integrates well with almost all technologies currently being used in my company.
It's scalable.
ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules.
The most valuable features of ODI are the knowledge modules, such as the Loading Knowledge module and the Check Knowledge module, they are helpful. We can check for the constraints in ODI. That helps in figuring out what are the constraints that are the primary keys created in the tables. We can check them with the Check Knowledge module.
The most valuable feature of ODI is the to use of the whole ETL to create a data lake.
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.
ODI's most valuable features are it utilizes the database engine and is very lightweight.
Oracle provides great documentation.
Easy to understand, very developer-friendly, and has a big forum community and lots of documentation for support.
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 scalability is great. It's one of the reasons we chose the solution.
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.
The most valuable feature that we use is the Knowledge Modules.
It's completely user-friendly.
It has the ability to easily load slowly changing dimensions.
The installation of the client ODI Studio is easy.
All our systems can be widely integrated by ODI, such as transactional systems, our data warehouses, and B2B integration.