Oracle Data Integrator (ODI) Reviews

The most common use of this solution is to connect to the database source and database target. Data in the repository constructs the mapping or programs to form the data into the target using the CAEM knowledge model. I'm a data warehouse analyst. 

The CAEM is very useful, particularly in its modularity and portability. We can also use real-time transformation to build and load data. It works more quickly than other ELTs and it's very simple and modular. It can be used for all integrations, not only AIT or ELT.

Reverse engineering is complicated when reversing from the database to the repository. It's pretty challenging to manage.

I've been using this solution for four years. 

The solution is stable. 

The solution is scalable.

To date, we haven't needed customer support. 

The initial deployment is very simple and we carried out the implementation in-house.

I rate this solution nine out of 10. 

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.

We use the solution to collect information from all sixteen sites to create a data warehouse data lake at the head office, accessible to everyone.

The most valuable feature is Data movement.

If you have something like Cisco on top of it, you will have endless problems.

Also, the price and integration could be improved.

I have been using Oracle Data Integrator (ODI) for years.

The product is stable if you have a working site. It offers great flexibility.

I rate the solution’s stability a ten out of ten.

The solution’s scalability is good.

You have to allocate more CPUs to scale further.

We evaluated Informatica, and we went with Oracle because the client was an Oracle user.

The initial setup is simple. There are several things to check with ODI. Prerequisites include space, database memory, CPU allocation, and so forth.

Deployment was done in-house.

Oracle has a huge benefit.

If you use it on any VM, it's very expensive.

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.

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.

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.

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.

ODI is used for reports. We feed the flat files into the solution to use them in reports. I create reports on the tables that are being loaded into the target tables.

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.

ODI could improve the ease of use. There is a steep learning curve to use the solution.

I have been using Oracle Data Integrator (ODI) for approximately two years.

ODI is stable and it's good to work with.

As the version of ODI is updated the solution scales. The scalability is based on the versions that are being provided for the product.

We have three to four people using the solution in my company.

I rate the technical support from ODI a four out of five.

Positive

I previously used Informatica and we switched because it did not support Oracle BI applications. If we stayed with Informatica we would have to use third-party tools.

The initial setup of ODI is not simple. We need to install Oracle BI applications to use ODI to access the tables that are built in or provided by Oracle. It is an on-premise system and it would help to make the process easier.

We use a consultant for the implementation of ODI.

We are having different environments for ODI and depending on many factors in those environments will dictate how many people we need. We have the development, testing, and production environment. We will need people for each of these areas. If it is a small firm or a mid-sized firm, and if the consultant has good knowledge, then they can manage the three environments, or else the work can be distributed. 

For the deployment, we use eight people. If the project is a small size project with fewer tables, then it can be even done with three people.

I recommend this solution to others. It helps to take training to use the solution.

I rate ODI an eight 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.