Oracle Data Integrator (ODI) vs. Oracle Warehouse Builder vs. SAP Integration Suite

Oracle Data Integrator is well suited in all the situations where you need to integrate data from and to different systems/technologies/environments or to schedule some tasks. I've used it on Oracle Database (Data Warehouses or Data Marts), with great loading and transforming performances to accomplish any kind of relational task. This is true for all Oracle applications (like Hyperion Planning, Hyperion Essbase, Hyperion Financial Management, and so on). I've also used it to manage files on different operating systems, to execute procedures in various languages and to read and write data from and to non-Oracle technologies, and I can confirm that its performances have always been very good. It can become less appropriate depending on the expenses that can be afforded by the customer since its license costs are quite high.

Incentivized

The best place for Oracle Warehouse Builder is at the business IT level. It's not suited for business-level users. They are easy confused. One way to reduce the confusion for the developers is to set up the workspaces based on the requirements that are discovered in design sessions. Once this is complete, the implementation of Oracle Warehouse Builder can take flight and be successful.

Incentivized

Good at: 1. Integrations with in SAP applications, especially with event based triggers 2. Can be integrated very well with other BTP services to attain Batch processing and store credentials 3. Supports many authentication models Improvements: 1. No version history available compared to as it is available in S4HANA 2. Need a lot of improvement in git hub connections

Incentivized

• Oracle Data Integrator nearly addresses every data issue that one can expect. Oracle Data Integrator is tightly integrated to the Oracle Suite of products. This is one of the major strengths of Oracle Data Integrator. Oracle Data Integrator is part of the Oracle Business Intelligence Applications Suite - which is highly used by various industries. This tool replaced Informatica ETL in Oracle Business Intelligence Applications Suite.
• Oracle Data Integrator comes with many pre-written data packages. If one has to load data from Excel to Oracle Database, there is a package that is ready available for them - cutting down lot of effort on writing the code. Similarly, there are packages for Oracle to SQL, SQL to Oracle and all other possible combinations. Developers love this feature.
• Oracle Data Integrator relies highly on the database for processing. This is actually an ELT tool rather than an ETL tool. It first loads all the data into target instance and then transforms it at the expense of database resources. This light footprint makes this tool very special.
• The other major advantage of Oracle Data Integrator, like any other Oracle products, is a readily available developer pool. As all Oracle products are free to download for demo environments, many organizations prefer to play around with a product before purchasing it. Also, Oracle support and community is a big advantage compared to other vendors.

Incentivized

• Easy transformation.
• Easy implementation from Oracle to Oracle systems.
• Ease of usage and easy to learn.
• Starting component of metadata management.

Incentivized

• The extensive catalog of pre package integrations that have in the discovery center. That allows developers to find solutions that can fit the needs.
• Monitor of the integrations and api deployed.
• API management has been for us a very usefull tool inside integration suite, to be able to have the API Hub with the documentation of our apis.

Incentivized

• ODI does not have an intuitive user interface. It is powerful, but difficult to figure out at first. There is a significant learning curve between usability, proficiency, and mastery of the tool.
• ODI contains some frustrating bugs. It is Java based and has some caching issues, often requiring you to restart the program before you see your code changes stick.
• ODI does not have a strong versioning process. It is not intuitive to keep an up to date repository of versioned code packages. This can create versioning issues between environments if you do not have a strong external code versioning process.

Incentivized

• What I noticed is that sometimes OWB doesn't generate the best SQL in the package especially when there are a high number of source tables in the ETL. It would be nice if ETL developers were allowed to update the generated packages in the database directly.
• Another thing - moving OWB ETLs from one database to another one could be easier - for example it would be nice to just copy the generated packages from one database to the other one without doing the deployment of these ETLs through OWB.

Incentivized

• Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
• Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
• Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective

Incentivized

It is maturing and over time will have a good pool of resources. Each new version has addressed the issues of the previous ones. Its getting better and bigger.

It is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.

Incentivized

The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.

Incentivized

The support for SAP Integration Suite is satisfactory. We leverage SAP support through our manage services partner. So far, we have not had many major issues. One concern, to make our rating a ten, would be turnaround time on high priority incidents. SAP Integration Suite drives our key business functions forward. Without a reasonable service level agreement on turnaround, we sometimes find us running into issues running pay, etc.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

I have used Trifacta Google Data Prep quite a bit. We use Google Cloud Platform across our organization. The tools are very comparable in what they offer. I would say Data Prep has a slight edge in usability and a cleaner UI, but both of the tools have comparable toolsets.

Incentivized

Ab>initio, IBM Datastage 8.0

Incentivized

Before deploying SAP Integration Suite, we assessed Oracle Financial Services Analytics and IBM Risk Analytics. While Oracle had proved its mettle in the exceptional database support and IBM in presenting risk model tools, SAP Integration Suite overwhelmed others by being effortlessly integrated with our existing banking framework.

• From a business intelligence perspective, it allows us to provide users with the necessary data and information to make informed decisions.
• Compared with other Oracle products and licensing, I do not think the pricing was unreasonable.
• It is part of a larger install, so for ease of use, we purchased it with other Oracle products.

Incentivized

• It improved understanding of ETL functions. Data is consistent. The speed is pretty good.

Incentivized

• Positive impact would be availability of pre-defined integration content via templates.
• One can re-use a template as a starting point to modify and adopt to client-specific integration flow.
• Availability of adaptors and connectors, making it easier to piece together the integration flow.

Incentivized