Oracle Data Integrator (ODI) Review

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


Valuable Features

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.

Improvements to My Organization

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.

Room for Improvement

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.

Use of Solution

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.

Deployment Issues

We experienced no issues with the deployment.

Stability Issues

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

Scalability Issues

We have been able to scale it for our needs.

Customer Service and Technical Support

Oracle technical support for this product is excellent.

Initial Setup

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.

Implementation Team

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

Other Solutions Considered

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.

Other Advice

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.



Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email