TrustRadius Insights for Oracle Data Integrator (ODI) are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
User-Friendly Interface: Reviewers have consistently praised the simplicity and user-friendliness of the interface, making it easy to navigate and utilize efficiently. The neat and clean design enhances the overall user experience, with users finding it particularly intuitive for extracting, transforming, and loading data.
Abundance of Transformation Options: Many users have highlighted the wide range of transformation options available, which significantly aids in completing tasks effectively and efficiently. These diverse options cater to different data handling needs, allowing users to work with large volumes of data from multiple sources seamlessly.
Scalability and Performance: The scalability and performance of the product have been commended by reviewers for handling high-volume batch load ETL processes and providing flexibility with big-data extractions. Users appreciate the top-notch scalability that enables them to tackle complex data integration tasks within one efficient tool.
Oracle Data Integrator (ODI) Reviews
9 Reviews
Professional, Scientific, and Technical ServicesInformation Technology & Services8Management Consulting1
We use data integrator to handle large amount of data, bulk batch loads,use it for data transformation and integration with different platforms.
We use this for our client request to fulfill their requirement.
We are working in insurance industry in which lots of data from different sources needs to be handled. It solve our purpose to mange large volume of data from different sources.
Pros
Extract, transform and load the data
Work well with large volume of data
Use with multiple sources
Cons
Bit difficult to use as compare to other tools
Sometime feels slowness while working
Likelihood to Recommend
Efficiently work with different platforms but we should have deep knowledge of tool.
Oracle Data Integrator is used in enterprise projects designed for data warehouse and ETL. It makes sense for us to use the ODI ETL product, especially since the databases we work with are usually oracle products. You can create individual ETL packages with the Oracle Data Integrator ETL product. You can schedule these ETL packets at certain time intervals. You can generate summary tables using aggregate functions in an Oracle Data Integrator product. In this way, you can create data march tables to be used in the data warehouse. The end-user interface of the Oracle Data Integrator product has an intricate appearance. The ETL design screen needs to be more straightforward and more user-friendly. Also, connections to databases other than Oracle can fail after certain periods of time.
Pros
There are enough aggregate functions to design a Data Warehouse. In this way, summary tables can be created.
Works compatible with Oracle databases. By making ODBC connections, database connections are made more stable.
Cons
The end user interface of Oracle Data Integrator ETL can be made simpler and more convenient.
Oracle external database connections are time out after a certain period of time. Therefore, data transfers can be disrupted.
Likelihood to Recommend
Oracle Data Integrator ETL product is efficient in projects where Oracle databases are heavily used. In the Oracle Data Integrator ETL tool, you can quickly transfer and transform data by connecting source and destination databases with ODBC. You can run your millions of data transfers separately by dividing them into multiple packages. This will give you performance results in data transfer operations. JSON can issue ODI ETL product errors with XML data or in oracle external databases. Sometimes the solution to these errors can cause serious time losses.
Oracle Data Integrator was used along with Oracle Goldengate product to consolidate data into Oracle database from other data resources in other DBMS and ETL jobs. The data was integrated or converted into using target format using Oracle Data Integrator.
Pros
Converts data from various sources into one target format using various business logic rules and integrates with various DBMS types.
Transformed data from DB2, SQL Server and other Oracle databases into flat files and then used ETL jobs to load into Oracle DB target
Data Integrator and Goldengate were used together to accomplish the data movement needed for business and data consolidation in live environment. Data Integrator helped with development and in reducing lead time to convert data into target.
Cons
Still complex product to use for ETL developers. Needed lot of training and testing before it could be implemented in production data conversion.
Initial set up was resource intensive on machine and manpower used on this project.
Better GUI interface with less options should be designed for Big data integration tool.
Likelihood to Recommend
Well suited for data consolidation into data warehouse type of database from multiple sources in real time.
VU
Verified User
Employee in Information Technology (Information Technology and Services company, 10,001+ employees)
In my organization, my department develops business intelligence solutions for our worldwide customers, whose business can be in any kind of sector. In this scenario, ODI is being used to integrate data among all the pieces of the software architecture, connecting Oracle and non-Oracle technologies.
In my 6 years experience, I used ODI to: - feed up relational environments, like Data Warehouses or Data Marts models with reporting purposes - feed up Hyperion Planning, Hyperion Essbase, Hyperion Financial Management or INFOR applications, for our customers' controllers - read data from Oracle and non-Oracle technologies (i.e.: SAP, SQL Server, INFOR, and many other), thanks to all ODI's connectors and interpreter - schedule tasks and workflow, independently from the operating system, thanks to ODI's agent (the service that controls all the tool's tasks).
ODI helps integrating data across different sources and targets, executing operating systems command, managing mistakes or discards, logging all the operations performed by the integration flows and scheduling those flows.
Pros
Is simple and easy to learn, thanks to the low number of development objects that it has (mainly: interfaces, procedures and packages, plus variables).
It allows you to integrate data from and to any kind of technology. This is a strong point since it's able to connect practically to any technology, Oracle and not.
It allows you to create integration flows that manage through steps on any task.
It provides both an automatic and a customizable management of integration mistakes.
If you feel stronger in developing through hard code, ODI allows you to integrate anything through procedures.
It supports almost any kind of developing language, like SQL, PLSQL, Java, Javascript, C#, and so on.
It's easy to backup, since it provides a native way to export all the developments but also its relational repositories (master and work) can be exported from the database where they reside.
Cons
The newest version (ODI 12c) has been released with some minor bug related to environment stability (i.e. connection loss).
After some time that you develop on ODI studio, you need to restart the program, since it tends to occupy a lot of RAM.
The ODI studio may need a machine with a lot of resources, otherwise it may become slow.
Likelihood to Recommend
Oracle Data Integrator is well suited in all the situations where you need to integrate data from and to different systems/technologies/environments or to schedule some tasks. I've used it on Oracle database (Data Warehouses or Data Marts), with great loading and transforming performances to accomplish any kind of relational task. This is true for all Oracle applications (like Hyperion Planning, Hyperion Essbase, Hyperion Financial Management, and so on).
I've also used it to manage files on different operating systems, to execute procedures in various languages and to read and write data from and to non-Oracle technologies, and I can confirm that its performances have always been very good.
It can become less appropriate depending on the expenses that can be afforded by the customer since its license costs are quite high.
Oracle Data Integrator (ODI) enabled us to assist our customers loading their data warehouse and get insights from their data both in batch mode or in real-time. We helped customers in various fields: finance, gambling, telecom, transportation, education etc.
Pros
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.
Cons
Continuous integration is missing and would be a really nice feature to enforce a good development lifecycle.
Better handling of files and folders, to be able to easily go through all the files of a folder.
Security setup is not easy to maintain.
Likelihood to Recommend
ODI can access a large range of technologies as source or target so it's suited for most of the loadings. For efficient change data capture and streaming, I would recommend other tools for the ingestion part though, like Oracle Golden Gate and Apache Kafka which are dedicated to that. File processing is not that easy in ODI so if it's your main use case you might want to look at another tool.
Oracle Data Integrator (ODI) is used to integrate applications, bulk data movement and of course to load a data warehouse environment.
ODI helped me to reduce a slowly changing dimension type 2 with the same output, from 22,000 seconds to 168 seconds. [I] Manage to load 10.000+ files to a table from 1000+ different sources under 20 minutes with approximate 300 GB of data per day.
Pros
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!
I managed to connect to an Ingress Database, within 3 days of time (it is not supported out of the box).
When a new version of source and/or target database supports new data types, it takes my 5 minutes to implement it into ODI and immediately start using it.
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. It takes your 3 days to learn ODI and be an "intermediate ODI Developer", if you know how to write SQL.
Big data connectors are implemented since 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.
Cons
They need to work on the multiuser development environment and include the ability to comply with different kinds of SDLCs.
Likelihood to Recommend
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. What else do you need?
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.
We are currently using ODI for large companies that have the need to generate and consolidate information, move data, transform and consolidate data.
The great quality of ODI, is that it is able to connect to any database and source (xml , txt, SOZ ) both source and target. ODI is all possible, we have not seen in the position of a customer asks us something that ODI can not do . Thanks to that we can modify its core, we can do anything.
ODI allows the multidisciplinary development, its own versioning, and integration with any language (Python , Groovy , t - SQL).
Pros
It connects to any source (database, files, web services) and target.
Modify the logic of SQL with knowledge modules.
Easy development.
Cons
The product sometimes have small bugs, which are fixed with patches.
Very complex queries are difficult to do in graphics mappings
It has functionality versions but can not develop in parallel a same object.
Likelihood to Recommend
Oracle Data Integrator (ODI) is recommended when you want to move data from heterogeneous sources. Also the multidisciplinary development is appropriate because when an object is being used, it appears locked by another user. ODI is a mature tool on the market.
A developer without advanced knowledge of SQL, can easily use the tool and generate complex queries against the database.
Oracle Data Integrator is used to extract data from various manufacturing machines, transform it into a usable form, and load it into a data warehouse for use by Oracle Business Intelligence reports. In this case, it was used to attempt a "real-time data warehousing solution," which is not necessarily its intended operation. Data was provided every hour, as required by the client. It was used across the whole organization to help with various decisions, including but not limited to manufacturing quality, resource tracking, accountability, and equipment usage.
Pros
Oracle Data Integrator is a very powerful tool. The graphical user interface simplifies the generation of complex SQL statements which can be used to extract and transform large amounts of data.
ODI allows users to structure and schedule packages of code. It allows you to combine data extraction and transformation sequences based on business area, relationships, or whichever design technique best suits your organization.
ODI is able to provide detailed logging information and send out alerts via email, simplifying the process of monitoring and debugging issues.
Cons
ODI does not have an intuitive user interface. It is powerful, but difficult to figure out at first. There is a significant learning curve between usability, proficiency, and mastery of the tool.
ODI contains some frustrating bugs. It is Java based and has some caching issues, often requiring you to restart the program before you see your code changes stick.
ODI does not have a strong versioning process. It is not intuitive to keep an up to date repository of versioned code packages. This can create versioning issues between environments if you do not have a strong external code versioning process.
Likelihood to Recommend
Oracle Data Integrator is a good solution for daily data warehousing needs. It is less suitable for business requirements that demand frequent data updates. Accessing static data with Oracle Data Integrator is much simpler than trying to extract, transform, and load dynamic data. It requires a skilled development team to use, so it is more appropriate in long term solutions where a team will be available to manage the code than it is for a short term solution.
In my prior role, I primarily used ODI as the ETL tool to transform data from relational systems or flat files into Hyperion Essbase. It was also the extraction tool from Essbase to various data marts/warehouses. ODI was used to map multiple source files/tables together, transform the data appropriately to align with Essbase nomenclature/naming conventions. ODI was also used as a scheduling tool to kick off command-line utilities specific to the Hyperion toolset and to manage interdependent data processing jobs for a given organization.
Pros
Transforms and loads large amounts of data (gigabyte and up).
Stores complex transformation logic in an understandable way that is easily updated after the fact.
Managed multiple ETL user groups/credentials to segment data availability and execution pathways.
Cons
ODI has a very arduous process for migrating components from one environment to another. I've found it to be error prone unless migrating a full schema which is not always a viable option.
ODI has no web-based administration panel, all admin tasks must be handled via hard install.
The scheduler tool is difficult to initially set up and not intuitive to manage. Takes a while to stand up properly.
Likelihood to Recommend
Oracle Data Integrator (ODI) is good when large amounts of data are to be processed and the ETL logic is maintained by a team of IT professionals. Where it loses out against other tools, is it cannot be managed by the data owner (i.e. finance) as the tool relies on SQL logic which is not always understood by the data owner. Coupled with the fact that it is not managed via the web but through hard install, it makes it difficult to diffuse ETL tasks from IT to the core business.
