Oracle Data Integrator (ODI) Reviews

Integration with all systems is easy with Oracle Data Integrator, and it is easy to use. I have not used any other product, but with Oracle Data Integrator, we can easily connect to an ERP system, an SAP system, or a cloud application.

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.

I have been using this solution for around seven years.

It is pretty good.

It is scalable.

I didn't contact them for the line breakage issue, but I have contacted them for other things. My experience with them was good. Their solution was quick and the response was quick. I would rate them a four out of five.

We have seen a return on investment with this product.

Everything is good, and I would rate it an eight 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.

Several projects benefited from the ODI data integration capabilities such as Loading OLTP system's data to Data warehouses, pulling data from cloud-based databases and loading to on-premises DW, for example: extracting data from a SQL server which is based on Azure infrastructure. 

Perform data integration from cloud to cloud.

Data migration between OLTP systems. 

Event-based integration such SOA, for example, BPEL performed calls of ODI scenarios based on EBS events.

All projects where I have implemented ODI solution highly benefited of high data volume integration.

There are several very important features that we use daily.

• All our systems can be widely integrated by ODI, such as transactional systems, our data warehouses, and B2B integration.
• ODI is really powerful for BI projects with traditional star-schema loads. For example, we integrated Salesforce to an Oracle data warehouse with it.ODI is a platform agnostic, you may have any data source and any target to integrate and ODI will enable you to connect.
• It facilitates real-time data replication from Microsoft SQL Server to an operational database sitting on Oracle Database.
• It provides for legacy systems integration. It integrates any SQL server database.

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

I've never had any issues with stability.

I haven't had any issues with scalability.

Technical service is a 6, and Oracle needs to improve this.

Besides ODI I have used SSIS and Power Center Informatica, both are similar and typical ETL tools, ODI up until 11g version had some differences, for example in ODI 11g we call the integration object as"Interface" wheres in  Informatica it is called "Mappings" which has been implemented in the ODI 12c version.

I still could see the Oracle solution being more robust and more logical, not to mention when it comes to customization, in ODI I felt more freedom to develop and customize the built-in code and designer objects such as the models, interfaces, for example, you can run updates in the repository tables"SNP's".

Also, ODI handles high data volume more efficiently, of course, your database must be well tuned a good hardware helps a lot. The other difference is that you have more flexibility to manage the ODI metadata since everything is based on database .

Getting the right JDK during agent config on Solaris was challenging on one occasion. It needs a Solaris expert to do this but in general when one knows the bits and pieces of the tool it should be straight forward .

I was usually part of the implementation team to implement the product .

oracle would better provide these kind of information .

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.

We use ODI for integration services from different systems, such as finance systems and online display systems. Additionally, we integrate it with the external partners with ODI. 

We use ODI in combination with the SFTP server.

The most valuable features of ODI are the ease of development, you can have a template, and you can onboard transfer very quickly. There's a lot of knowledge modules available that we can use. If you want to connect, for example, a Sibyl, SQL, Oracle, or different products, we don't have to develop them from scratch. They are available, but if it's not, we can go into the marketplace and see if there's a connector there. Having the connector available reduces the amount of hard work needed. We only have to put the inputs and outputs. In some of the products, we use there is already integration available for ODI, which is helpful.

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.

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

Since we moved to the new version, ODI has been very stable, and we haven't had any unplanned outages. We only have had planned outages, I'm pretty happy with it.

The only issue we have had recently was when we patched ODI all the jobs that were supposed to be scheduled at 6:00, it ran seven hours earlier. It's a result of the patch. We were working with Oracle and they gave us a fix.

The solution is scalable, we can increase the agents and let it do more work.

We have approximately 12 people using the solution in my organization.

We use this solution extensively without our organization.

The technical support is very good. f you give them all the information, they seem to give you a solution pretty quickly. We have not had any issue with the support. However, we are using paid support and I am not sure if the regular support is the same.

I've used other solutions previously, such as Microsoft tools, they are much easier to set up. ODI is a bit clunky to begin operations, it requires a longer learning curve.

We are using this solution extensively.

The initial setup is complex, it took us three months.

We reached out to Oracle and a few other partners that Oracle has but, in the end, we decided we should do it ourselves. If we did not do it ourselves we wouldn't have the knowledge of how to do it in the future. We received a quotation from them and then decided, we would do it ourselves, in-house.

For all these cloud products, we have to patch them ourselves, it is not done automatically. I was expecting patching to be automatic but it is not. 

The solution is expensive because of the model they use. The cost is for the license and for support.

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.

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

The ODI topology and designer are the most valuable features. The topology gives me total freedom in switching between technologies / ETL agents. The mapping designer gives me a good graphical overview of ETL mappings.

The speed in which we create/generate our ETL mappings has increased by at least a factor of four as compared to Oracle Warehouse Builder.

Overall performance needs improvement. Especially when running ODI clients on Windows desktops. ODI seems to generate a lot of network traffic.

ODI Studio can be very slow. Objects (mappings, packages, tables, etc.) can take minutes to open for editing when you are running ODI Studio on a Windows client when you have your repository database running on a server. It gets even worse when you are working on the same repository with multiple developers, which is not uncommon. :) The solution to this problem is running the ODI Studio in a virtual desktop on the same database server.

I have used it for over two years.

Migrating from 12.1.2 to 12.1.3 did not go as smooth as it should.

Sometimes the ODI agent shows running in WebLogic (middleware), while it cannot be reached by the ODI clients.

More than six or seven developers working in the same repository is the maximum.

Oracle support does not always seem to deliver. At one time during the migration of 12.1.2 to 12.1.3, we had issues taking over six months to resolve.

We previously used Oracle Warehouse Builder, which was discontinued by Oracle. Oracle Data Integrator is Oracle's strategic choice for ETL tooling going forward. We could not risk running out of support. That is why we had to buy licenses for Oracle Data Integrator (whereas Oracle Warehouse Builder came free with the Oracle database - until version 11.2).

The initial setup is really not straightforward. You really have to think about the architecture in which you want to use ODI (i.e., agent(s), repository setup, topology). But this makes the software as flexible as it can be.

As with all Oracle products, you need a licensing specialist to look at your needs.

We considered moving forward with Oracle Warehouse Builder, but dismissed OWB because it was running out of support.

We also considered Informatica PowerCenter, but it seemed to be even more expensive an option than ODI. With ODI, we could still use some of the present Oracle skills (mapping design), so the learning curve seemed less steep compared to Informatica.

• Think about the architecture in which you are going to use ODI very well.
• Think about where to place an agent and, if possible, put your ODI repository as close to this agent as possible.
• If possible, run your agent closer to the target than to the source.
• Try splitting up your repository into multiple work repositories for groups of developers of no more than five developers.