My advice would be to consider the impact of Oracle's slow performance on daily operations and be aware of the pricing implications of their cloud services for periodic usage.
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.
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.
I have a strong bias for Oracle Data Integrator. It is a fantastic tool with automation, dynamic coding, and scalability features. While it was great on-premise, Oracle has been slow to modernize it. However, they are now making efforts to improve its user experience and automation in the cloud. ODI is up-to-date with cloud-based solutions and supports various technologies and databases. It has a web-based interface and can be deployed in high-availability clusters. ODI's Knowledge Modules are vital in integration projects. They help create mappings, manage transformations, and generate SQL for Oracle metadata. By automating tasks and combining code and graphical elements, they make integration smoother and more efficient. ODI handles data quality and consistency by allowing you to create elements within the mapping to ensure quality. You can use dummy referencing and build data quality modules as needed. While it is not a click-and-go tool, it offers flexibility to tailor data quality measures to your specific needs, making it more like traditional data warehousing. It is hard to say if ODI is the best option on the market. It was a top choice in the past, but with evolving technologies and diverse cloud options, its position may vary. While it is strong in Oracle's cloud, other platforms like Azure might offer different advantages. Additionally, solutions like Snowflake provide more comprehensive offerings than just data integration tools like ODI. Overall, I would rate ODI as a nine out of ten. I would recommend it to others.
The knowledge module is reusable but needs to be more relevant. First, we create an ODS and data structures, such as a Snowflake or a Star schema. We move data as quickly as possible while ensuring that we do not reprocess already moved data. Therefore, we only handle data that is newly created or modified. Overall, I rate the solution a nine out of ten.
DBA at a comms service provider with 201-500 employees
Real User
Top 20
2023-11-28T13:39:06Z
Nov 28, 2023
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.
Learn what your peers think about Oracle Data Integrator (ODI). Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
I give Oracle Data Integrator a ten out of ten. We have around 25 users. For environments with simple architecture, one person is sufficient for the maintenance of Oracle Data Integrator. Oracle Data Integrator is well-suited for large organizations; however, it may present complex integrations when dealing with heterogeneous source systems and different types of source data, especially without a skilled staff capable of adopting a rational approach to ODI. 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.
Based on the customer's requirement, I would recommend the solution to them. In our company, we have prior experience with ESBs. We can suggest multiple ESB options that are best suited to the customer's needs. Overall, I rate this solution an eight out of ten.
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.
Technical lead at a transportation company with 10,001+ employees
Real User
2022-10-31T15:02:05Z
Oct 31, 2022
My company has around ten users of Oracle Data Integrator (ODI). A team of two to five people handles the deployment and maintenance of the solution. The current client of my company has this plan of moving to the cloud, with the possibility of replacing the ETL tool altogether, which could mean that more data is coming up, so there may be a plan to increase the usage of Oracle Data Integrator (ODI). My advice to others looking into implementing Oracle Data Integrator (ODI) is that if your database is on Oracle or SQL server, then Oracle Data Integrator (ODI) is a good tool to use. My rating for Oracle Data Integrator (ODI) is seven out of ten.
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
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.
Like any product I'd try to understand how that product's roadmap might fit with your technology journey. If you're looking at ODI strategically, and get time to talk with Oracle Product Management. Whilst I can speak for all PMs in the organization those that I have dealt with are interested in understanding your needs, journey - you may express a unique position, or actually find that you're not the only one with the need.
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.
I would recommend using ODI if we are using an Oracle Database as your data warehouse, or as your primary database only. If not then I wouldn't recommend ODI to be used. I have seen the newer cloud version and I think it is more user-friendly than the older versions. I rate Oracle Data Integrator an eight out of ten.
Principal Consultant at a tech services company with 501-1,000 employees
MSP
2022-01-24T18:43:22Z
Jan 24, 2022
ODI is very friendly to those who have been traditionally writing a scale PL/SQL. It has lots of connectors to many different sources, although the target databases it supports are relatively limited compared to Informatica. It's also easier to understand, very developer-friendly, and has a big forum community and lots of documentation for support. I would rate it as nine out of ten.
Applications Support Manager at a marketing services firm with 1,001-5,000 employees
Real User
2021-11-18T08:59:58Z
Nov 18, 2021
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.
Banking Excellence - Predictive Analysis at a financial services firm with 11-50 employees
Real User
2020-10-28T13:43:06Z
Oct 28, 2020
We're simply an Oracle customer. We don't have a business relationship with the company. There's no specific version of the solution that we use. I wouldn't recommend any other services above Oracle. Overall, I would rate the solution eight out of ten.
Big Data / Business Intelligence / Datawarehousing at DWgrain (Client Health BIS)
Consultant
2016-05-04T06:03:00Z
May 4, 2016
The setup of the environment requires experts on site, but it is very worth it since at first for customers it can be quite complex. The vendor needs to enable the customer on a frequent basis during implementation, but the results are great.
EPM/BI certified Consultant, Oracle ACE and TeraCorp Consulting CEO at TeraCorp Consulting
Consultant
2016-05-01T11:30:00Z
May 1, 2016
Because Oracle products are development frameworks, your final results are as good as the people that implemented it. Make sure that your implementation team is the best it could be, at least for the first implementation. If something is implemented incorrectly at the start, it'll cost you a lot more to fix than to build a new system from scratch. Sometimes it can be so badly designed that it is impossible to fix. I've been working on implementations for 21 years and I have seen bad implementations everywhere. In fact, I have seen the same tools implemented in the same team by two different people, with one being a success and the other a failure. In the same company, one department says that the tool does not work for them and another says that the tool is the best. The only difference was the implementer. Make sure you get a good team to implement it. The tool has its flaws but most of time (99%) it is the implementer's fault that you have a bad or slow model.
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...
My advice would be to consider the impact of Oracle's slow performance on daily operations and be aware of the pricing implications of their cloud services for periodic usage.
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.
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.
I have a strong bias for Oracle Data Integrator. It is a fantastic tool with automation, dynamic coding, and scalability features. While it was great on-premise, Oracle has been slow to modernize it. However, they are now making efforts to improve its user experience and automation in the cloud. ODI is up-to-date with cloud-based solutions and supports various technologies and databases. It has a web-based interface and can be deployed in high-availability clusters. ODI's Knowledge Modules are vital in integration projects. They help create mappings, manage transformations, and generate SQL for Oracle metadata. By automating tasks and combining code and graphical elements, they make integration smoother and more efficient. ODI handles data quality and consistency by allowing you to create elements within the mapping to ensure quality. You can use dummy referencing and build data quality modules as needed. While it is not a click-and-go tool, it offers flexibility to tailor data quality measures to your specific needs, making it more like traditional data warehousing. It is hard to say if ODI is the best option on the market. It was a top choice in the past, but with evolving technologies and diverse cloud options, its position may vary. While it is strong in Oracle's cloud, other platforms like Azure might offer different advantages. Additionally, solutions like Snowflake provide more comprehensive offerings than just data integration tools like ODI. Overall, I would rate ODI as a nine out of ten. I would recommend it to others.
The knowledge module is reusable but needs to be more relevant. First, we create an ODS and data structures, such as a Snowflake or a Star schema. We move data as quickly as possible while ensuring that we do not reprocess already moved data. Therefore, we only handle data that is newly created or modified. Overall, I rate the solution a nine out of ten.
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.
Overall, I rate the solution a seven out of ten.
I give Oracle Data Integrator a ten out of ten. We have around 25 users. For environments with simple architecture, one person is sufficient for the maintenance of Oracle Data Integrator. Oracle Data Integrator is well-suited for large organizations; however, it may present complex integrations when dealing with heterogeneous source systems and different types of source data, especially without a skilled staff capable of adopting a rational approach to ODI. 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.
Based on the customer's requirement, I would recommend the solution to them. In our company, we have prior experience with ESBs. We can suggest multiple ESB options that are best suited to the customer's needs. Overall, I rate this solution an eight out of ten.
I rate this solution eight out of 10.
I rate this solution nine out of 10.
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.
My company has around ten users of Oracle Data Integrator (ODI). A team of two to five people handles the deployment and maintenance of the solution. The current client of my company has this plan of moving to the cloud, with the possibility of replacing the ETL tool altogether, which could mean that more data is coming up, so there may be a plan to increase the usage of Oracle Data Integrator (ODI). My advice to others looking into implementing Oracle Data Integrator (ODI) is that if your database is on Oracle or SQL server, then Oracle Data Integrator (ODI) is a good tool to use. My rating for Oracle Data Integrator (ODI) is seven out of ten.
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.
I recommend this solution to others. It helps to take training to use the solution. I rate ODI an eight out of ten.
I rate this solution seven out of 10.
Like any product I'd try to understand how that product's roadmap might fit with your technology journey. If you're looking at ODI strategically, and get time to talk with Oracle Product Management. Whilst I can speak for all PMs in the organization those that I have dealt with are interested in understanding your needs, journey - you may express a unique position, or actually find that you're not the only one with the need.
I would give ODI a rating of nine 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.
Everything is good, and I would rate it an eight out of ten.
I would recommend using ODI if we are using an Oracle Database as your data warehouse, or as your primary database only. If not then I wouldn't recommend ODI to be used. I have seen the newer cloud version and I think it is more user-friendly than the older versions. I rate Oracle Data Integrator an eight out of ten.
ODI is very friendly to those who have been traditionally writing a scale PL/SQL. It has lots of connectors to many different sources, although the target databases it supports are relatively limited compared to Informatica. It's also easier to understand, very developer-friendly, and has a big forum community and lots of documentation for support. I would rate it as nine out of ten.
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're simply an Oracle customer. We don't have a business relationship with the company. There's no specific version of the solution that we use. I wouldn't recommend any other services above Oracle. Overall, I would rate the solution eight out of ten.
I think different tools have their own pros and cons, so it all depends on your overall needs.
The setup of the environment requires experts on site, but it is very worth it since at first for customers it can be quite complex. The vendor needs to enable the customer on a frequent basis during implementation, but the results are great.
Because Oracle products are development frameworks, your final results are as good as the people that implemented it. Make sure that your implementation team is the best it could be, at least for the first implementation. If something is implemented incorrectly at the start, it'll cost you a lot more to fix than to build a new system from scratch. Sometimes it can be so badly designed that it is impossible to fix. I've been working on implementations for 21 years and I have seen bad implementations everywhere. In fact, I have seen the same tools implemented in the same team by two different people, with one being a success and the other a failure. In the same company, one department says that the tool does not work for them and another says that the tool is the best. The only difference was the implementer. Make sure you get a good team to implement it. The tool has its flaws but most of time (99%) it is the implementer's fault that you have a bad or slow model.