We are using a graphical tool called PowerDesigner to create logical and physical models. From that, we create code that can be run by Oracle Data Integrator, which then maps the data based on these models and sends it to its destination. It is currently very integrated with Oracle.
We use the product to extract data from various sources like EBS and Fusion, transform it, and load it into data warehousing systems supporting Azure, Salesforce, and KPIs.
We use the product to transfer data from one stage to another of the data layers. It helps move data from different layers, transform, manage, and put the proper timestamp on the managed data.
Learn what your peers think about Oracle Data Integrator (ODI). Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
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.
Director - Data Analytics / EPM at Constellation Consulting Group
Real User
Top 20
2023-02-13T20:29:49Z
Feb 13, 2023
Our main use case is getting data from operational systems. We are integrators and implement this solution for our customers. I'm the company's director of analytics.
The most common use of this solution is to connect to the database source and database target. Data in the repository constructs the mapping or programs to form the data into the target using the CAEM knowledge model. I'm a data warehouse analyst.
Applications Support Manager at a marketing services firm with 1,001-5,000 employees
Real User
2021-11-18T08:59:58Z
Nov 18, 2021
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.
We have been using Oracle Data Integrator for populating Financial Services Data Warehouse. Data extraction is done into a staging area from different source systems and then this data is validated and certain quality checks have been performed here. We used Oracle Data Integrator data quality checks builtin capability to perform these different data quality checks. Then data is consolidated and transformed into the staging area and finally gets landed into the data warehouse. I also used this for generating data hand-offs for other applications.
Assistant Manager - MIS Analyst at TCS Private Limited
Real User
2019-05-05T21:16:00Z
May 5, 2019
Our primary use for this solution is a data integration and merging tool. It easily connects to many databases like MySql, SQL Server, etc. It's completely user-friendly. We can easily manage packages, ETL, and Procedures.
Multiple data sources: "Most" of them, Oracle databases (some MS SQL, some Sybase, lots of files and some web services). Because the environment was overwhelmingly Oracle, ODI (we started from OWB) was a much better and cost-effective solution for us than Informatica.
We use ODI to integrate data from the OLTP database to the data warehouse. The source database systems including Oracle, MySQL, flat files... Our business background is OTA and the total data is about 100T.
Big Data / Business Intelligence / Datawarehousing at DWgrain (Client Health BIS)
Consultant
2016-05-04T06:03:00Z
May 4, 2016
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.
We mainly use ODI to integrate all of our EPM applications, which includes Essbase ASO/BSO cubes, Hyperion Planning, DRM and HFM applications. Also it is used to manage a custom data warehouse developed in Oracle DB which is used as source for OBIEE reporting.
Oracle Data Integrator (ODI) is a data integration software solution that provides a unified infrastructure to streamline data and application integration projects. It uses a powerful design approach to data integration, which separates the declarative rules from the implementation details. The solution is based on a unique ELT (Extract Load Transform) architecture, eliminating the need for a standalone ETL server and proprietary engine.
Oracle Data Integrator Features
ODI has many...
We are using a graphical tool called PowerDesigner to create logical and physical models. From that, we create code that can be run by Oracle Data Integrator, which then maps the data based on these models and sends it to its destination. It is currently very integrated with Oracle.
We use the product to extract data from various sources like EBS and Fusion, transform it, and load it into data warehousing systems supporting Azure, Salesforce, and KPIs.
We use the product to transfer data from one stage to another of the data layers. It helps move data from different layers, transform, manage, and put the proper timestamp on the managed data.
We use the solution to collect information from all sixteen sites to create a data warehouse data lake at the head office, accessible to everyone.
We are using the solution for ETL purposes for our data warehouse.
We use the solution for getting transactions and BI reports for stakeholders.
We use Oracle Data Integrator as an integration tool for our data warehouse.
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.
Our main use case is getting data from operational systems. We are integrators and implement this solution for our customers. I'm the company's director of analytics.
The most common use of this solution is to connect to the database source and database target. Data in the repository constructs the mapping or programs to form the data into the target using the CAEM knowledge model. I'm a data warehouse analyst.
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.
I primarily use ODI as a tool for data integration and data warehousing.
Our ODI usage is expensive and is mainly for the extraction transformation and loading (ETL) of data from multiple sources to a data warehouse.
I'm a technical manager and we provide technical services to our customers. We are partners with Oracle.
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.
We primarily use the solution for digital health and sometimes automation tasks.
We have been using Oracle Data Integrator for populating Financial Services Data Warehouse. Data extraction is done into a staging area from different source systems and then this data is validated and certain quality checks have been performed here. We used Oracle Data Integrator data quality checks builtin capability to perform these different data quality checks. Then data is consolidated and transformed into the staging area and finally gets landed into the data warehouse. I also used this for generating data hand-offs for other applications.
We use this solution for Data Integration in Data warehouse projects.
Our primary use for this solution is a data integration and merging tool. It easily connects to many databases like MySql, SQL Server, etc. It's completely user-friendly. We can easily manage packages, ETL, and Procedures.
To have a common ETL tool in the DW team, start a common way of ETL development, set up a process registry, and daily process flow.
Multiple data sources: "Most" of them, Oracle databases (some MS SQL, some Sybase, lots of files and some web services). Because the environment was overwhelmingly Oracle, ODI (we started from OWB) was a much better and cost-effective solution for us than Informatica.
High volume batch loads to move data from transactional systems into the decision support warehouse.
We use ODI to integrate data from the OLTP database to the data warehouse. The source database systems including Oracle, MySQL, flat files... Our business background is OTA and the total data is about 100T.
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.
Very large and complexes environments implementation, 10000+ users with 24x7 global operation and multiple EPM tools working in sync.
We mainly use ODI to integrate all of our EPM applications, which includes Essbase ASO/BSO cubes, Hyperion Planning, DRM and HFM applications. Also it is used to manage a custom data warehouse developed in Oracle DB which is used as source for OBIEE reporting.