The Oracle Data Integrator interface is extremely slow, especially when using remote desktop connections. This impacts user experience significantly when trying to manage large repositories of metadata. Additionally, the pricing model for Oracle Cloud Services is not cost-effective for periodic usage.
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.
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.
ODI could improve by focusing on streamlining its features without unnecessary overhead. It could also enhance seamless integration with data catalog and other tools, similar to what IBM offers with Infosphere. Additionally, strengthening integration with Oracle Analytics Services would be beneficial. In the next release of ODI, I would like to see a focus on fixing existing features and ensuring that bug fixes from previous versions don't reappear. Improving metadata management could also be beneficial. Overall, a stronger commitment to software quality and release consistency would be a major improvement.
Learn what your peers think about Oracle Data Integrator (ODI). Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
There is an automated method for handling errors in the load process. However, at present, when multiple steps are executed in parallel in the load plan and errors occur, the error handling mechanism does not function correctly. This issue can be improved.
In our company, we haven't tried consuming services from IoT in our company yet, and I would like to know if the solution will support IoT services in the next release. Specifically, I'd like to see if the solution will support us in acquiring data from our databases.
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.
Technical lead at a transportation company with 10,001+ employees
Real User
2022-10-31T15:02:05Z
Oct 31, 2022
An area for improvement in Oracle Data Integrator (ODI) is real-time integration. Currently, my company has a workaround to implement real-time integration, an area on which Oracle must focus more. Real-time integration should be easier in Oracle Data Integrator (ODI). Another area for improvement in Oracle Data Integrator (ODI) is integration with more publishers and subscribers rather than just database integrations. Oracle Data Integrator (ODI) has features that support at least ninety percent of my organization, so it's only real-time integration that I'd like to see in the next release of the solution.
Manager- Application and Cloud Services at a tech services company with 501-1,000 employees
Real User
2022-10-18T08:37:16Z
Oct 18, 2022
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.
SAP Business One Project Manager at a consumer goods company with 11-50 employees
Real User
2022-02-07T18:39:20Z
Feb 7, 2022
I think Oracle should add more functions to improve optimization. Automation should be improved to enhance the product. Some of our customers carry out data comparisons between Oracle and other features and Oracle is lacking in some of those tools and features.
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.
ODI could improve by being more user-friendly. Informatica, which is also an ETL tool, similar to ODI, but Informatica is very user-friendly, easy to use, and simple to integrate, compared to ODI. ODI has many features, put them all together, and sometimes we get confused about which ones to use, which ones not to use.
Applications Support Manager at a marketing services firm with 1,001-5,000 employees
Real User
2021-11-18T08:59:58Z
Nov 18, 2021
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.
Banking Excellence - Predictive Analysis at a financial services firm with 11-50 employees
Real User
2020-10-28T13:43:06Z
Oct 28, 2020
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.
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.
* ETL process registry solution is missing. * To manage dependencies between loading packages. * Versioning logic and release process are not well supported.
The ODI scheduler for agent sometime fails with no sign, which impact the ETL solution severely. The property window in the ODI studio always does not refresh as it should. Sometimes, the mapping or package automatically gets edited.
Big Data / Business Intelligence / Datawarehousing at DWgrain (Client Health BIS)
Consultant
2016-05-04T06:03:00Z
May 4, 2016
There is always room for improvement, even when something is really good, but I think ODI is one of the best ETL tools in the market. However, I've always waited for the web service feature to be improved in next versions, so at last the 12C version the web service has been improved, some of the limitations of the 11g version were solved. Also, it would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons, although it looks like the cloud option offers some extra connectors (for example, in Salesforce CRM).
EPM/BI certified Consultant, Oracle ACE and TeraCorp Consulting CEO at TeraCorp Consulting
Consultant
2016-05-01T11:30:00Z
May 1, 2016
Right now, we have two very different GUIs - 11g and 12c. 11g is faster to develop than 12c as it takes more steps to do exactly the same as 11g, but you have a lot of things that you need to do yourself. 12c implemented some things for which you have to use some specialized code automatically, like parallel data load, but it is slower to develop. For me, the best thing would be to merge the GUI from 11g into the capabilities of 12c.
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.
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...
The Oracle Data Integrator interface is extremely slow, especially when using remote desktop connections. This impacts user experience significantly when trying to manage large repositories of metadata. Additionally, the pricing model for Oracle Cloud Services is not cost-effective for periodic usage.
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.
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.
ODI could improve by focusing on streamlining its features without unnecessary overhead. It could also enhance seamless integration with data catalog and other tools, similar to what IBM offers with Infosphere. Additionally, strengthening integration with Oracle Analytics Services would be beneficial. In the next release of ODI, I would like to see a focus on fixing existing features and ensuring that bug fixes from previous versions don't reappear. Improving metadata management could also be beneficial. Overall, a stronger commitment to software quality and release consistency would be a major improvement.
If you have something like Cisco on top of it, you will have endless problems. Also, the price and integration could be improved.
The initial setup is a bit complex compared to other tools.
Stability could be improved because some operators have issues.
There is an automated method for handling errors in the load process. However, at present, when multiple steps are executed in parallel in the load plan and errors occur, the error handling mechanism does not function correctly. This issue can be improved.
In our company, we haven't tried consuming services from IoT in our company yet, and I would like to know if the solution will support IoT services in the next release. Specifically, I'd like to see if the solution will support us in acquiring data from our databases.
The initial setup could be easier and it would be helpful if they'd reduce licensing costs.
Reverse engineering is complicated when reversing from the database to the repository. It's pretty challenging to manage.
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.
An area for improvement in Oracle Data Integrator (ODI) is real-time integration. Currently, my company has a workaround to implement real-time integration, an area on which Oracle must focus more. Real-time integration should be easier in Oracle Data Integrator (ODI). Another area for improvement in Oracle Data Integrator (ODI) is integration with more publishers and subscribers rather than just database integrations. Oracle Data Integrator (ODI) has features that support at least ninety percent of my organization, so it's only real-time integration that I'd like to see in the next release of the solution.
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 think Oracle should add more functions to improve optimization. Automation should be improved to enhance the product. Some of our customers carry out data comparisons between Oracle and other features and Oracle is lacking in some of those tools and features.
ODI could improve the ease of use. There is a steep learning curve to use the solution.
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.
ODI could improve by being more user-friendly. Informatica, which is also an ETL tool, similar to ODI, but Informatica is very user-friendly, easy to use, and simple to integrate, compared to ODI. ODI has many features, put them all together, and sometimes we get confused about which ones to use, which ones not to use.
An area for improvement would be the lack of SQL compatibility - ODI has no ability to interact with SQL unstructured types and data types.
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.
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.
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.
The performance of the user interface is in need of improvement.
Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts.
* ETL process registry solution is missing. * To manage dependencies between loading packages. * Versioning logic and release process are not well supported.
* Click intensive on mapping * Lots of mouse clicking * GUI could be improved.
It lacks a suite of tools suitable for fully processing data and moving it into decision support warehouses.
The ODI scheduler for agent sometime fails with no sign, which impact the ETL solution severely. The property window in the ODI studio always does not refresh as it should. Sometimes, the mapping or package automatically gets edited.
There is always room for improvement, even when something is really good, but I think ODI is one of the best ETL tools in the market. However, I've always waited for the web service feature to be improved in next versions, so at last the 12C version the web service has been improved, some of the limitations of the 11g version were solved. Also, it would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons, although it looks like the cloud option offers some extra connectors (for example, in Salesforce CRM).
Right now, we have two very different GUIs - 11g and 12c. 11g is faster to develop than 12c as it takes more steps to do exactly the same as 11g, but you have a lot of things that you need to do yourself. 12c implemented some things for which you have to use some specialized code automatically, like parallel data load, but it is slower to develop. For me, the best thing would be to merge the GUI from 11g into the capabilities of 12c.
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.