Oracle Data Integrator (ODI) Reviews

The use case involved integrating a GMI-specific solution, which was a customer requirement. We used the software provided by the customer for this purpose. However, within our organization, we consumed some of the services by using Oracle.

I will need to involve the integration team to elaborate on the features, as they can provide input. I work mostly on the functional-technical side. However, in Oracle Data Integrator, the governance, especially the service governance, is good. There is also a schedule-based data-pulling mechanism. The message-pulling mechanism in the solution is good, and we can define threshold limits on top of the services. For instance, if I publish some equipment gateway or email gateway, the end user can consume a specific number of services from the solution.

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.

I have been using Oracle Data Integrator for the past two years in a customer implementation process where the solution was required. Also, I have experience with the solution's commercial version. I am a solutions consultant.

Stability-wise, I rate this solution a seven out of ten.

In our organization, we have not checked whether Oracle Data Integrator is scalable, including whether it is vertically or horizontally scalable or can scale automatically. However, we can deploy and configure it. We have only worked with Oracle Data Integrator in one of the deployments. At the same time, we were involved with Pentaho Data Integration for the other deployments. To ensure the solution's maintenance, we require a staff of three technical experts, including an integration expert and an ESB expert.

We haven't had any experience with the solution's technical support team. Also, technical support-related affairs are taken care of by a different team.

We have used WSO2 Integration for a proof of concepts (POC) in our organization. We have also used Red Hat Fuse and Pentaho Data Integration. So, we have worked on these tools from an ESB point of view. Also, commercial ESBs like Oracle Enterprise. We primarily used Red Hat Fuse for APM and ACM, deployed specifically for one of our customers between 2015 and 2016. So, our recent experience is with Pentaho Data Integration and Hitachi Pentaho Data Integration.

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. Pentaho Data Integration and Hitachi Data Integration are also good.

Since the deployment of Oracle Data Integrator has already been done, the customer provides the platform or software. Another team is responsible for maintaining the solution while we have published some of its services. It takes around three months to deploy the solution.

Our company didn't have to pay for the license of the solution since our customer had already paid for it.

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.

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.

I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support.

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.

I've been using Oracle Data Integrator (ODI) for more than seven years.

Oracle Data Integrator (ODI) is a stable solution.

Oracle Data Integrator (ODI) is a scalable solution.

The technical support for Oracle Data Integrator (ODI) is good. Here in Turkey, you can directly contact support, and the support team is knowledgeable about the solution.

The Oracle Data Integrator (ODI) technical support team is a four for me on a scale of one to five.

The initial setup for Oracle Data Integrator (ODI) is straightforward.

The Oracle Data Integrator (ODI) pricing isn't expensive, but it's not cheap, so it's in the middle. I'd rate the pricing as three out of five.

We evaluated Informatica and Microsoft SSIS.

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.

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.

We had an opportunity to set up a data warehouse. We were doing a complex stack of Oracle. The customer was using Oracle as their backend database.

It can extract all day. It doesn't look after any particular database. It is not platform-dependent, and that's the main thing that makes it really useful.

It has good plug-ins.

The studio was quite useful.

It was a user-friendly product.

The product is stable. It's scalable. 

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've used the solution for two or three projects. I last used it less than a year ago.

This is a very, very stable product. It's reliable. There are no bugs or glitches, and it doesn't crash or freeze. 

The solution can scale well.

I haven't created any tickets through support. However, my understanding is that, once you open a ticket, they will ask many, many questions, and they do resolve things. It can just be frustrating when you need a problem solved, and they just keep asking questions. There's a bit of going back and forth.

We are actually moving away from Oracle, as it's not very reasonable cost-wise.

What you can do on ODI, for example, can be done on SSIS from Microsoft too, which is free of cost.

In terms of the initial setup, at first, it was a bit hard for me. That said, it is pretty straightforward once you are done with this data source connection tool and once you are done with this on the repository side. Setting up a reporting server was easy, however, doing the middleware, especially on the application server, was a bit tedious for me.

I'd rate the setup process a four out of five in terms of ease of implementation.

It's quite an expensive solution. We'd like it if they could adjust the pricing according to the region they are operating in. 

Per user, it is $900 USD per year, though they will give some discount. However, even a 60% to 70% of discount for each won't help us much. On top of that, there is the perpetual license you must pay at the outset.

I'd rate the cost at a one out of five in terms of affordability.

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 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.