I have used ODI to improve run-times of many corporations' overall integration run-times. Corporations on a daily basis run integration jobs which normally take five hours or more. I have seen these jobs become hourly jobs because of the time reduction they received with ODI's involvement.

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.

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.

For the EPM environment, the ODI is the key to transforming a good project into a great project. With ODI, we can make all the EPM tools work together as one and we can create a puzzle that will increase the performance and capability of all EPM tools. We can have an integrated environment and decrease the close time from two days to one hour.

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

Oracle Data Integrator offers a declarative style ETL development, where you mainly use pre-built knowledge modules for doing integration tasks. As a developer, you don't need to focus on how part of the integration, you only focus on what to do. You just need to configure certain components as per your requirements and underlying execution plan and code is generated for you. For every technology there are knowledge modules available, the best optimal code is generated which eventually gets executed on database level. Our developers created best performing ETLs with very little effort leveraging this feature.

It allows a single skill set to handle virtually all of the data transport and transformation needs of a company. It moves the ETL processing to where the data resides and saves network traffic and the need for dedicated transformation engines - hardware that needs to be purchased, managed and supported.

We hadn’t upgraded in a long time, so all of our business users were creating their own solutions with spreadsheets, for example. We realized we were behind and purchased a whole stack of Oracle products that have simplified the way we move and track data. The accountants enjoy being able to reconcile where the data is and how it is changing. That’s the reason we bought the tool.

We spend much less time developing integrations because all we need to focus on is the business logic.

Before using ODI, I was forced to develop programs with multiple technologies (Java, Python) to extract data from multiple sources. Now with ODI, I just have to configure the knowledge module to perform the extraction.

This automation using Knowledge Modules has improved our organization.

We use ODI to extract and transform data to load into our data warehouse from our source system, which is Oracle EBS. We have found that it's very efficient; very fast. We can easily customize and review even out-of-the-box analytics that came with Oracle. We’re able to easily go in and modify and correct any anomalies that we have.

The features that we have applied to our project has helped us reduce manual effort and increased our scalability and growth. I worked on multiple domains where requirements were adversely different. We used many ODI features to enhanced our data transformation capability.

The learning curve is a little less because if you are already in the ELT business, you know how it works. Overall, it's good.

My organization develops solutions using all the Oracle EPM products, and ODI has helped us to integrate all the different technologies.

We use ODI to integrate all Oracle EPM suite used in our financial area. ODI is the core engine used to move data across different applications every day. It’s by far the most important architectural element in our BI/EPM environment since all data passes through it.

Far more efficient and robust than OWB, (it was the natural evolution for us).

I work in a consulting role but I believe that by implementing it a lot of organizations’ manual processes have been automated

The main improvement was unifying and standardizing ELT processes. For example, each table in the EDW solution has a set of standard columns used solely for auditing, data lineage and debugging purposes. Because the code to support those columns is shared across the whole solution, we are now capable of getting the auditing information for every single piece of data in the entire solution, without having to code it individually for each stream.

I don't know why we have different database environments, but we do. The business wants the data to be collected in one place, so they can do reporting and so on.

This product can be installed on a desktop or a server to be operated. v10 has a local database that allows you to train a client for its use. This, of course, provides good knowledge transfer.

It worked fine, but we needed a tool that would include quality and master data seamlessly.  This is more of a standalone ETL tool.

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.

With ODI 11, I have spent time developing different interfaces at the same time instead of developing them one by one. ODI doesn't have an interpretable language in its architecture, so if you know Oracle you can write mapping SQL statements that you need for getting the data. This allows you me to have a greater adaptability.

My customers started to increase their ETL performance with great margins. This was especially the case when ODI was used with Exadata, which allows each statement to be executed much faster.

Thanks to the flexbility of the tool, we could build 3 mappings using variables and the substitution API in replacement of 300 mappings in Oracle Warehouse Builder. It's much easier to maintain!

Any IT company that relies on data coming from its clients or internal users requires data maintenance. All that collected data should be able to provide insight into the various behaviors of the clients across different platforms. For us, ODI has been key in collecting, transforming, and storing information from our various sources.

It has streamlined and automated data loads, and exports from our ERP system to our finance data warehouse and to Hyperion Essbase. The post-data load tie-back to the source system was also performed using this tool. The tool has also made metadata management more efficient, and automated the process from relational source to Hyperion Essbase.

This product helps our customers achieve their goals and objectives.

Before adopting this solution we used to work hard. We now feel better because our manual work is completely over. 

In our DW/BI solution, ODI is the main tool to integrate the data as a daily batch. Besides loading data, we do most of our transformations in ODI. ODI is quick to use.

We replaced many manual actions and tasks with mappings in Oracle Data Integrator, and created schedules, and then used SOA Suite services to automatically transfer large data amounts between different systems.

We are Oracle partners. We have our clients and they need this solution. We implement it according to the clients' requirements.

We added DevOps to ODI.

You can use the ODI versioning or our component, and complement both with lifecycle management, fully-automated deploy and integration with issue tracking.

ODI has made it possible for our organization to rapidly build robust integrations that process large data. The learning curve of this technology is also very smooth and can be picked up by any one with minimal programming experience.

• It increased ETL development efficiency 1/3 in time.
• It has a short learning curve for newcomers, compared to previous MS DTS packages and scripting.

The tool is declarative, and it only runs on the target staging databases, so I have full control over it and I can change the SQL that the tool generates. I do not have to maintain a separate ETL instance. I can change the SQL when something is not performing correctly.

The old fashion PL/SQL codes have been translated into ODI, improving the way of maintenance. Several developers can work on the same project easily.

In our experience with ODI, we've found that the best use of it was with the development of our data warehouse.

We had a customer whose core business was a logistics suite. ODI was used for their reporting purpose in some key BI reports such as "Container Load Plan (CLP) Reports", "Master Data Management Reports", "Business Partner Reports - Non Shipper Reports ", "Customer Consignee Details Reports". The customers requirements were delivered by using OTM (Oracle Transportation Management) as the Source OLTP System by us. We were also able to integrate ODI with their transactional system and therefore, we generated the reports through an ETL & data warehousing model. Due to this, the customer was able to get a deep-dive insight into their business performance across the south-east Asian logistics industry.