Oracle Data Integrator (ODI) Reviews

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

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.

Oracle Data Integrator (ODI) integrates with the cloud, but the 12C version only can be integrated with the cloud. The best part of the ODI is, it does not have its own ETL engine of its own, it utilizes the database engine itself.

We use ODI for data integration only, such as extraction, transformation, and loading of data from different sources into one particular database. Additionally, we use ODI for our data warehouse.

ODI's most valuable features are it utilizes the database engine and is very lightweight.

ODI's ability to connect multiple types of database environments from a particular server, place, or system is beneficial. I can connect to many databases, such as Dev, UAT, production, or user acceptance test databases. All together in only one place. It's all about changing the context in that particular application. The moment you change the context, the ODI will start processing the data from different environments altogether.

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.

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

The stability of Oracle Data Integrator is very good.

ODI is scalable, it is a matter of your configuration. If you configure the tools properly it is scalable.

The solution can be used for small to large enterprises.

I have been satisfied with the technical support.

I have used other solutions previously.

ODI has one of the easiest implementations out of all the others for a database.

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.

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.

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.

Now, ODI has Cloud Service which you can deploy your repositories to Oracle Data Integrator Cloud Service for you to use both on prem, Big Data and cloud environments.

Oracle Data Integrator (ODI) can support any type of databases that has a jdbc driver in a native way. I have accessed and retrieve data from an Ingress database. Big data connectors are implemented to 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.

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

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.

They need to work on the multiuser development environment and include the ability to comply with different kinds of SDLCs.

I've been using it for more than 10 years, since Oracle acquired Sunopsis.

There were no issues with the deployment.

I've experienced no issues with performance. Since sky is the limit, you can do what you want to do within ODI in several ways.

It's been able to scale for our needs. ODI will fit your needs.

10. I generally create a service request per year and they are being solved within a week.

They're very efficient.

We switched because of ODIs impressive increasement in development productivity.

It was straightforward and very easy. Almost the same as setup>next> next>next.

In-house.

Worth every penny.

There are various options in licensing, either per seat or per target core count. It depends how you want to use it.

We also looked at Informatica Power Center, AbInitio, Business Objects Data Integrator (BODI), and SQL Server Integration Services (SSIS).

If you want a robust, flexible solution with no extra hardware that is easy to learn, then ODI is the right product for you. 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.

The most value feature of this product are the Knowledge Modules. Oracle Data Integrator comes with a comprehensive library of Knowledge Modules that helps automate the data flow, reduce the learning curve, and shorten the implementation time.

The use of this product has helped identify data quality issues in upstream source systems. As a result, data quality rules have been implemented in order to capture them during data entry.

I would like to see in the next version/release the ability to scale a package workflow or data flow process during the execution at run time. Once a workflow is developed, a snapshot of the code is taken and a scenario is created. It is the scenario that is executed during run time. In order to add a step to the package workflow, you must modify it and re-create another scenario. Thus, making such changes to package workflow can impact other packages that are dependent.

I have used this product for more than 13 years. I was first exposed to this product back in 2003. Before Oracle Corporation purchased the product, it was formerly known as Sunopsis. I learned to develop workflow packages with version 3.

We experienced no issues with the deployment.

It’s a perfectly stable product and we’ve not experienced any issues.

We have been able to scale it for our needs.

Oracle technical support for this product is excellent.

Although the initial setup was straightforward, you must decide if you will create one schema for the master and work repository or separate schemas. However, the product provides a step-by-step menu-driven UI, which makes the installation a breeze.

The implementation was done by both a vendor and internal resources. In addition, name standards for objects (e.g., packages, scenarios, procedures) should be considered and each package should be design independently from other packages (e.g., Modular Programming).

MS SQL Server Integration Services (SSIS) was considered. However, the internally-preferred vendor company was Oracle. The availability of a license and expertise in product usage helped in the decision-making process.

The most important decision is the deployment strategy of the Master and Work Repositories that is the use of Single or Multiple Master Repositories. The company’s internal policy will determine which strategy can be used. However, the most common implementation I have seen is multiple master and work repositories. It performs and works as advertised.

We use the solution for getting transactions and BI reports for stakeholders.

Stability could be improved because some operators have issues.

I have been using Oracle Data Integrator for two years and a half.

We used the solution, and we didn't have any problems with that.

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

We didn't have a problem with the tool’s scalability. There are six to seven people using this tool in our organization. We don't have plans to increase the usage. It responds to all our problems.

We didn’t contact the customer support team. We figure it out by ourselves.

The initial setup is easy. It took about two and a half months to deploy.

We set up the tool in an environment because of data sensitivity.

Overall, I rate the solution a seven out of ten.