Oracle Data Integrator for Oracle Business Intelligence - license

Mfg. Part: L100376 | CDW Part: 4271119 | UNSPSC: 43232304
Request Pricing

Have leasing questions? Let us know how can we help.

Note: Leasing is available to organizations only. Leasing is not available to individuals.
Mon-Fri 7am-7:30pm CT
Ships same day if ordered before 4 PM CT
  • License
  • Named User Plus
  • UNIX
  • Win
View More
Product Overview
Main Features
  • License
  • Named User Plus
  • UNIX
  • Win
Oracle Data Integrator is a comprehensive data integration platform that covers all data integration requirements: from high-volume, high-performance batch loads, to event-driven, trickle-feed integration processes, to SOA-enabled data services. Oracle Data Integrator provides superior developer productivity and improved user experience with a redesigned flow-based declarative user interface and deeper integration with Oracle GoldenGate. ODI further builds on its flexible and high-performance architecture with comprehensive big data support and added parallelism when executing data integration processes. It includes interoperability with Oracle Warehouse Builder (OWB) for a quick and simple migration for OWB customers to ODI. Additionally, ODI can now be monitored from a single solution along with other Oracle technologies and applications through the integration with Oracle Enterprise Manager.

Technical Specifications
Specifications are provided by the manufacturer. Refer to the manufacturer for an explanation of the print speed and other ratings.
System Requirements
Platform: UNIX , Windows

License Category: License
License Qty: Named User Plus
License Type: License

Brand: Oracle
Compatibility: PC
Manufacturer: Oracle Software
Model: For Oracle Business Intelligence
Packaged Quantity: 1
Product Line: Oracle Data Integrator

Category: Business applications
Installation Type: Locally installed
Subcategory: Business - databases / database tools

Product Reviews
Rated 4 out of 5 by 24reviewers.
Rated 4 out of 5 by I have used it to improve run-times of many corporations' overall integration run-times. Valuable Features:The Knowledge Module (KM) is my favorite feature of ODI. This is where I learned how to use variables to make jobs dynamic. I took that knowledge and created a KM that would go into iTunes and pull the sales of eBooks. Making something that is reusable, like a KM, is important to not only reduce build time but also maintenance in the future.Improvements to My Organization: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.Room for Improvement:Error handling can always be improved with ODI. A lot of the errors are generic, but I will say that with a little experience, you can decipher the errors to help you fix them. In fact, I find myself not using the debugger that came out with 12c, just because I have learned to read "ODI-login-eze."If there was a way to keep the basic user from creating a monster SQL that kills a system on execution, that would be great as well.Use of Solution:I have used it for 10 years. It's hard to believe it has been that long, but time flies when you have fun -- and I actually have fun when developing integration solutions. I started out on 10g and was able to quickly pick up on the ELT model after working with ETL for years before that. I was one of the first to install 11g on Red Hat. The main reason for the upgrade to 11g was purely looks as there were very little actual enhancements beside a couple of tools.12c was a major overhaul. I love working with 12c as it's now a flow-based tool but still ELT. It brings me back to the days of Hyperion Application Link (HAL), except that 12c isn't slow.Deployment Issues:It is seamless. You would have to really try to mess up the deployment.Stability Issues:Stability is good, better than 10g and 11g.Scalability Issues:Scalability-wise, 12c is the best in it's class. I could hand 12c to any size client and they would be fine developing and maintaining it.Technical Support:I think that you get more than the regular Oracle support when you are working with ODI. Even the "First Responders" have a very wide knowledge on the product. This is a pleasant change from some of the other products for which you get the person who asks if your computer is plugged in.Previous Solutions:I work on all the other integration products as well as ODI. In fact, I had to compare all the integration products (ODI, SSIS, HAL, Informatica, DataStage) when we were trying to decide on the strategic direction for the major bank that I was working for. HAL was being sunset, so easy decision there. DataStage cost a lot to host and was hard to develop in. Informatica was not installed anywhere in the corporation so the knowledge base for us wasn't there, so it got the boot too. It really came down to SSIS and ODI. We had a lot of SSIS knowledge and I was the only ODI developer. I took someone who never seen SSIS and ODI before, but had basic database knowledge, sat them in front of a computer, and gave them a day course on both. To be fair, after each course they had them create a job to do the same load. Results were clear and ODI won hands-down. ODI won out because of price, support, and speed/ease of development.Initial Setup:In 12c, they have made the setup so much more simple then what it used to be. The interface to do the setup walks you through every setup step.Implementation Team:I have been on both sides of the fence for this question. I would always have a vender do the install if you have never used the product before. There are a lot of little tweaks that can be made that takes experience with the tool to know these tweaks. If you have had the product for over a year, I would say, that in-house would be ok. Just make sure that if you have to remediate the install that you involve Oracle in that process so you make sure that all the parts get cleaned up properly otherwise the reinstall could be problematic.Cost and Licensing Advice:I would say that you need to pay attention to the licensing to make sure that you are not paying to much. Normally, the licensing can be your friend if you don't need ODI for anything complex. You can switch ODI to go back to ETL if you don't want to spend that much money. Thin about it this way, if you are charged for only where it translates the data, then put a 4-core Red Hat in the middle of everything. Force your jobs to translate only on the Red Hat server. Your 1 million dollar implementation just went to 200k -- you're welcome. The caveat with the ETL setup is that the processing is slower per job -- you're not welcome. Again, ask yourself, what do I really need this for?Other Advice:Know what you are getting into.If you are going to use a firm to build out a solution, ask for a Proof of Concept and ask them to show you how flexible it can be. If they can't quickly come up with something, be wary. Don't just go with someone that is cheap, you get what you pay for.This snapshot is to turn on automapping. This is a very useful function to have on when developing. This will make the magic happen when you connect a source and a target together. This is not in the documentation, so good luck finding how to turn it on if you haven't used it before.Disclaimer: My company has a business relationship with this vendor other than being a customer:We're implementation partners. October 17, 2016
Rated 4 out of 5 by The topology gives me total freedom in switching between technologies / ETL agents. Valuable Features: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.Improvements to My Organization: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.Room for Improvement: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.Use of Solution:I have used it for over two years.Stability Issues: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.Scalability Issues:More than six or seven developers working in the same repository is the maximum.Technical Support: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.Previous Solutions: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).Initial Setup: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.Cost and Licensing Advice:As with all Oracle products, you need a licensing specialist to look at your needs.Other Solutions Considered:We considered moving forward with Oracle Warehouse Builder, but dismissed OWB because it was running out of support.We also considered Informatica PowerCenter ( https://www.itcentralstation.com/products/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.Other Advice:* 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.Disclaimer: I am a real user, and this review is based on my own experience and opinions. October 17, 2016
Rated 5 out of 5 by 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. Valuable Features:It's the best tool for data integration. It can do anything you want, but the only downside is that you need to know what you are doing. You can take 10 times longer to do the same thing if you don't know how to use the tool.You have to know how to change the KM, how to use the dynamic coding, how to create dynamic models, and so on. In a lot of places, I see people using ODI wrongly, but the good thing about the tool is that isn't hard to fix common mistakes. With this you can improve performance, and in some cases, more than 10 times.Improvements to My Organization: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.Room for Improvement:Right now, we have two very different UIs - 11g and 12c. 11g is faster to develop than 12c as it takes more steps to do exactly the same as 11g, but you have a lot of things that you need to do yourself.12c implemented some things for which you have to use some specialized code automatically, like parallel data load, but it is slower to develop. For me, the best thing would be to merge the UI from 11g into the capabilities of 12c.Use of Solution:I've been using it for over 10 years.Deployment Issues:We have had no issues with the deployment.Stability Issues:There were issues mainly because of a Java memory leak.Scalability Issues:We have had no issues with scaling it for our needs.Technical Support:The technical support for EPM is bad. I don't remember anytime that the service support helped me with something. The problem is bigger when you have an environment with more than one product like Hyperion Planning and ODI.This happens because the products have different owners within Oracle and then different supports, and because of this, if you open a trouble ticket of loading data to planning and you say the words ODI, you'll be pushed around the two separate support teams indefinitely, even if your company has an Oracle support director just for you.Initial Setup:The bigger the environment, the bigger the challenge is you need to face. Maybe one day Oracle will integrate all their tools. It'll be easier, and the good thing is that I saw a lot of improvements over the years.Cost and Licensing Advice:All tools are expensive, but I think ODI is the most expensive since it depends on your sources and target databases. I think the best way to go is by doing packages and try to include free tools (if you buy Planning you have an ODI for BI licenses for free) or try to get discounts from your Oracle supplier. It's always good to explore what could happen if you get another tool or hardware together. Sometimes, you get more for less than if you get just one tool. Just be careful to not buy things that you won't use.Other Solutions Considered:I'm a consultant and my only evaluation was on the database. I decided on Oracle because of the database and during my career, their other tools are starting to come naturally.Other Advice:Because Oracle products are development frameworks, your final results are as good as the people that implemented it. Make sure that your implementation team is the best it could be, at least for the first implementation. If something is implemented incorrectly at the start, it'll cost you a lot more to fix than to build a new system from scratch. Sometimes it can be so badly designed that it is impossible to fix.I've been working on implementations for 19 years and I have seen bad implementations everywhere. In fact, I have seen the same tools implemented in the same team by two different people, with one being a success and the other a failure. In the same company, one department says that the tool does not work for them and another says that the tool is the best. The only difference was the implementer. Make sure you get a good team to implement it. The tool has its flaws but most of time (99%) it is the implementer's fault that you have a bad or slow model.Disclaimer: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer:We're platinum partners. October 1, 2016
Rated 3 out of 5 by Review about Oracle Data Integrator (ODI) Valuable Features:relational database to multidimensionalRoom for Improvement:need more roboust funcioning and easy of use for development using reusable jobsUse of Solution:1 yearDeployment Issues:noStability Issues:noScalability Issues:yesCustomer Service:goodTechnical Support:goodImplementation Team:vendor team using HackettOther Solutions Considered:yes looked at FDMEEOther Advice:needs improvement with reusablityDisclaimer: I am a real user, and this review is based on my own experience and opinions. September 30, 2016
Rated 4 out of 5 by I can readily develop processes that use relational, file, XML, JMS messaging, web and big data sources or targets. Valuable Features:The most important aspect of the product is the ability to work with almost any data source or target. I can readily develop processes that use relational, file, XML, JMS messaging, web and big data sources or targets.I can control the style of integration through "knowledge modules", and if they don’t do exactly what I want. I can write my own or customize the Oracle supplied ones.The ability to execute third-party (or in-house developed) Java code by installing JAR files allows a great deal of flexibility; for example, I can add custom processors to do access web APIs that use token based authentication.Another key feature is that we do not need to pass our data through some form of ETL engine hosted on a server; in some cases for example transforming data within a data warehouse all of the processing is done in single SQL queries thus reducing network traffic.Finally, the rich SDK supplied with ODI allows developers to create virtually any form of development or deployment automation.Improvements to My Organization: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.Room for Improvement:There needs to better support of external version control software, currently only SVN is present, but I hear the GIT is planned in future patch.From a DevOps point of view it would be useful to add better separation between ‘code’ and ‘executable’ exports, at the moment a piece of code will contain the embedded executable which bloats any source control objects (this may only be relevant to those the develop their own source and code control processes).Use of Solution:I've been using it for the last 10 years.Deployment Issues:We've had no issues with deployment.Stability Issues:12cR2 is a new version, and there are a few issues with stability, but I expect most to be resolved in the first patch.Scalability Issues:There have been no issues with the scalability.Technical Support:I rarely engage with support.Previous Solutions:As an independent consultant, I work with other ETL products, and switching is requirement of my employers. However, of the products I used recently (Informatica and Talend), I feel ODI gives me the most flexibility.Initial Setup:Set up of ODI Studio and the ODI repository is relatively simple, it is all done through a single JAR file executable. The complexity comes when you need to create ODI agents - there are three flavors of agent and the best choice of agent will depend on your agent management needs and infrastructure. The ODI agent executes ODI code and interacts with the host OS, typically one agent is sufficient, but more may be needed.Cost and Licensing Advice:The licensing model has changed a few times over the years - read the Oracle price list or speak to sales.Other Advice:Plan your ODI infrastructure, especially where data is transformed to ensure you get the best balance between license costs and performance. Get your developers trained in best practices so that avoid unnecessary pit falls.Disclaimer: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer:?I am an Oracle ACE and occasionally write technical articles or present at conferences. Oracle has no editorial control on my writing. Oracle may offer me hospitality.? September 28, 2016
Rated 4 out of 5 by All our systems can be widely integrated by ODI, such as transactional systems, our data warehouses, and B2B integration. Valuable Features: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.* 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.Room for Improvement: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 the web service feature to be improved in version 11G but there were some limitations . 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 Sales force CRM).Deployment Issues:I've never had any issues with deployment, but it's really helpful if the DBA supporting the environment has minimal knowledge of what ETL/ODI is, etc. Communication between database admins and users is really important.Stability Issues:I've never had any issues with stability.Scalability Issues:I haven't had any issues with scalability.Technical Support:Technical service is a 6, and Oracle needs to improve this.Initial Setup:Getting the right JDK during agent config on Solaris was challenging on one occasion. It needs a Solaris expert to do this, although it was improved in version 10G.Other Advice: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.Disclaimer: I am a real user, and this review is based on my own experience and opinions. July 7, 2016
Rated 5 out of 5 by The features that we have applied to our project have helped to reduce manual effort and increase our scalability. Valuable Features:The main features we use and has helped us to implement our ETL process are* Data transformation* In memory engine* KM customization* User friendly GUI* Versioning* Big Data support* Security support* Easy deployment* Reusable Mapping* Multiple Target Load* ELT Architecture* Application Server support for other vendor servers such as IBM WebsphereImprovements to My Organization: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.Room for Improvement:I am personally satisfied with current version, however, I think they should be able to provide a feature where we can easily use a configuration tool for TFS, GIT etc. This is essential for code management.Use of Solution:I've been using it for six years.Deployment Issues:We have had no issues with the deployment.Stability Issues:There have been no performance issues.Scalability Issues:It's been able to scale for our needs.Customer Service:9/10Technical Support:8/10Previous Solutions:I have not used any other product. However, I have seen other ETL tools in use such as BODS, SOA, and Informatica and I did not like them as I did not that they were user friendly.Initial Setup:It was straightforward. I used an application server for the initial setup and I did not find any challenges.Implementation Team:We performed an in-house one. If you have a technical team for ODI, then they can easily perform any implementation. If not, then you should have the vendor perform your implementation.ROI:10/10Cost and Licensing Advice:It is not as costly as other ETL tools.Other Advice:You should use Oracle Data Integrator for your data transformation, or at the very least give it a try.Disclaimer: I am a real user, and this review is based on my own experience and opinions. June 9, 2016
Rated 4 out of 5 by It uses the power of the source or target database to actually perform the ETL processing. Valuable Features:The biggest feature for ODI is the fact that it uses the power of the source or target database to actually perform the ETL processing. So a typical data integration tool might have its own ETL engine, and that would be an additional server, additional costs, something else you have to maintain. ODI actually has the ability to create and generate code that runs potentially on your Oracle database, or even on a big data target, on Hadoop or somewhere like that. So, you have that flexibility, and you don't have to have that additional cost in maintenance.A couple other additional benefits of Oracle Data Integrator would be the use of what's called a knowledge module. So this is like a code template that uses the metadata that you have available within ODI, and within your mapping, to generate that code, that then can be executed, like I said before, on the source or target system. The code'll be generated in the native format of that database or that technology. So, again, you have sort of a hands-off.These knowledge modules are built in. They can be developed and modified. So, the biggest thing, I always think, with ODI is, it fits around your data warehouse needs. Rather than taking your production, or your business, and trying to make it fit a tool, you do the opposite. You make the tool fit your business.Room for Improvement:One thing that is included, and it's going to improve, is the integration with a configuration management tool. Right now, they integrate with Subversion. And we know in the future, there's going to be more tools implemented there for configuration management and some new features there. So right now, it's kind of one of those features that, it's been released, but it's sort of a beta version of that feature where a lot more functionality will be coming down the line.Stability Issues:So ODI is actually quite a stable product. As a testament to the product team that develops it, they're not going to release something that is extremely buggy or things like that. So, I do see that often they will release features that are highly anticipated and highly sought after. And they might release them a little early. So there's definitely patching that comes into play there, to kind of get the full solution there.As far as stability, the Oracle Data Integrator has agents that run either in WebLogic, as a Java deployment there, or on a server as a Java agent, or a Java deployment. As long as a client has had the product implemented, with no issues there. So that's kind of the key there, you don't want to have those agents have a blip or any issues.Scalability Issues:So as far as scalability of Oracle Data Integrator, from the high availability standpoint, if you use WebLogic for your agent, you can use the clustering capability within WebLogic to create multiple nodes on different WebLogic servers. And then run your agent through that process there. So if something fails, if the main agent fails, it can fail over to the secondary agent or, again, another agent in your cluster.Technical Support:I'd probably put them up there around an eight, yeah. Being a system integrator of Oracle products, typically I'm on behalf of a client. So oftentimes it depends on who your client is and what their level of support is, as far as response and how things go. But I've always had great response with those guys.Previous Solutions:A lot of the projects I've worked on recently are Oracle VM apps projects. So, it's the folks that are in the Informatica version of VI apps, and looking at moving to the latest and greatest, which has Oracle Data Integrator behind the scenes. I'm not saying they're actually talking about using Informatica, they're just, that's what they have. And they're looking to migrate. Quite often where we come into play, ODI is typically chosen at that point. And then they call us in to help with it.Implementation Team:It's not too difficult. It's tough to look at it from the perspective of someone who hasn't been doing it for a while. And oftentimes, that's what you need to kind of make that determination. But as far as just getting up and running, you can get it installed, configure an agent, quite quickly. And then the next step would really be getting ready to build a mapping. And they actually introduced in the most recent release, or maybe even when 12C came out, they introduced a feature that would basically get everything, topology, the models, all the data stores, everything, ready to go for you, just in one simple wizard. And then you could actually start building mappings quickly.A lot of it is when they have home-grown ETL processes. So they'll manually script their ETL code. It's basically something that's difficult to maintain. So we talk about how we can use ODI to keep everything centralized. And even if we're not using ODI to actually build out mappings within the product, we might still be able to run that PL SQL or whatever it is, the script for ETL, from within ODI.So we still have everything consolidated and contained and then the other approach, or reason for moving to ODI, would be the need to get off of that middle tier integration server. That we don't need with ODI.Other Solutions Considered:As far as why consider Oracle Data Integrator, I think the big thing is the ability to consolidate all of your ETL into one place. Whether it's an Oracle to Oracle, source to target load, or even Oracle to Hadoop, or anything in between. SQL Server, MySQL, XML. ODI can basically talk to all of those different technologies. From a consolidation of all of your data warehouse or your data integration, if you will. And also, just use the same approach for mapping and creating processes for all of those different types of solutions. You have everything logically defined. And so when you're developing, it actually doesn't look any different than an Oracle source, and target doesn't look any different than a Hadoop source and target.Other Advice:So I would rate ODI a nine. And that's really because, just looking across the other ETL tools, so I mentioned Informatica, there's a lot of other ones out there. I've seen what ODI does from a sort of a declarative design approach, and the push-down of work to the source and target. I've seen that replicated in other tools that have come out after Oracle Data Integrator. That's a big key.It puts it kind of at the top, if you're going to look at a scale across all of the ETL tools. The other aspect to that rating is how they're integrating a lot of the big data technologies now. And it's a big deal from an Oracle standpoint, it's kind of how things are going. And it also just makes sense to, again, keep everything consolidated in one place. You already have an investment in ODI, it makes sense to try to drive some of your other big data type Hadoop loads or whatever it may be from that same place.Disclaimer: My company has a business relationship with this vendor other than being a customer:We're a partner. May 30, 2016
  • 2016-10-25 T09:41:40.777-05:00
  • bvseo_lps, prod_bvrr, vn_prr_5.6
  • cp-1, bvpage1
  • co_hasreviews, tv_24, tr_24
  • loc_en_US, sid_4271119, prod, sort_default
2 3next>>
Adding to Cart...
10/25/2016 9:44:16 PM
^ Back to Top

Maximum 300 characters
An account manager will email you within one business day to confirm your request.

Your Quote has been submitted

What Happens Next? A confirmation email is on its way. Within one business day, you will be contacted by an Account Manager to finalize your quote.


Something went wrong.

Please try again later.

License Selector

    The license selector is not currently available. Please try again later.