96

Oracle Data Integrator Enterprise Edition - license

Mfg. Part: L89218 | CDW Part: 3153582 | UNSPSC: 43232304
Request Pricing
Close

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

Note: Leasing is available to organizations only. Leasing is not available to individuals.
800.808.4239
Mon-Fri 7am-7:30pm CT
Availability:
Ships today if ordered within 5 hrs 52 mins
  • License
  • Named User Plus
View More
Product Overview
Main Features
  • License
  • Named User Plus
Oracle Data Integrator Enterprise Edition delivers high-performance data movement and transformation among enterprise platforms with its open and integrated E-LT architecture. Including built-in connectivity to all major databases, data warehouses, service oriented architectures, business intelligence, Oracle Data Integrator Enterprise Edition helps lower total cost of ownership among data-centric architectures. An easy-to-use interface combined with a rich extensibility framework helps improve productivity and lower development costs. Oracle Data Integrator Enterprise Edition is fully integrated with Oracle Fusion Middleware, Oracle Database, and Exadata to put data at the center of your enterprise.

Technical Specifications
Specifications are provided by the manufacturer. Refer to the manufacturer for an explanation of the print speed and other ratings.
Software
License Category: License
License Qty: Named User Plus
License Type: License

Header
Brand: Oracle
Compatibility: PC
Manufacturer: Oracle Software
Model: Enterprise Edition
Packaged Quantity: 1
Product Line: Oracle Data Integrator

General
Category: Business applications
Subcategory: Business - databases / database tools

Product Reviews
Oracle Data Integrator Enterprise Edition - license is rated 4.0 out of 5 by 28.
Rated 4 out of 5 by from The user interface is the most valuable feature. It is intuitive. Valuable Features:The user interface for the data integrator tool is probably the most valuable piece. I'm a relatively newcomer to the ODI. We opted to use ODI instead of Informatica. Relatively, I do not have a lot experience with a lot of VARs, but I've been able to understand a lot more about the direction Oracle is heading through the tool. It was very intuitive. It helps to have a good background in data manipulation, but it's very intuitive and has given a good appreciation of what the tool can do.Improvements to My 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.Room for Improvement:Perhaps more learning resources related to ODI would be helpful. I'm not sure if that's what restricted the buy-in. Even though the product has been out for 4-5 years, there are still a lot of people who aren't using it or have opted to stay with Informatica. It could be because there aren't enough self-study or self-research resources related to the product. That surely could be improved in the near term.Use of Solution:We've had it implemented for two years.Stability Issues:Any stability issues I've had, have been related to the data itself. It really depends on how whomever has implemented the product. If it stands up, it works well.Technical Support:We get very good and very timely response from technical support. Maybe, we just don't have very complicated questions, but we get very, very good response; very quick answers.Previous Solutions:We decided to move away from Informatica after we attended an Oracle conference about three years ago. We learned a lot more about where Oracle was going with it. One of the key reasons was not just moving forward with the newer technology; it was also because of the compatibility with the applications we use versus the applications that were available in Infomatica.We have the capability to extend it to other data sources, all of the non-standard data sources. We don't have to build out huge data structures in order to feed them in through Infomatica. We can read Excel spreadsheets and a bunch of other sources.Initial Setup:As a customer to a consultant team, I was involved in the installation and deployment of ODI. There were some challenges, which was probably due to the relative inexperience of the team that handled it. Eventually, they were able to get through it. Fortunately, my internal team as costumers were also able to do our research and participate in that discovery, too.Other Advice:You would have to evaluate what your key purpose is, and your existing, internal talent and experience. It's my belief that you should always try to have internal talent that is very confident, rather than having to always rely on consultants. If your talent has the experience in Infomatica – I don't think Infomatica is going anywhere – then it might be the best choice for you. I don’t think your office will fall apart. I think you have to evaluate which one will work for you.We were new customers to data integration, so we decided to go with newer technology that had already come from the same source.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2016-12-19
Rated 4 out of 5 by from With the Knowledge Modules, we're able to create our own reusable integration strategies for connecting to RDBMS, Hadoop, cloud services, etc. Valuable Features:The EL-T approach that will first load into the target dataserver before doing the transfer is a great architecture improvement compared to standard ETL tools that use a staging area and usually process the data in Java. With ODI, almost all the job is pushed down on the underlying technology, for instance the Oracle database or the Spark server.The Knowledge Module approach provides an easy and reusable way to create our own integration strategies. It's easy to create these Knowledge Modules to connect to new technologies, for instance.ODI is really the tool for any kind of integration because it speaks the language of the technology we connect. We can work with RDBMS but also in Hadoop, cloud services, flat files, web services, etc.Improvements to My Organization: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!Room for Improvement:- Development Lifecycle- native REST integration- Easier securityUse of Solution:5 yearsStability Issues:A bit unstable and buggy in the 12.1.2 release, but most of it is fixed in 12.1.3, so I would definitely recommend to jump to that version.Previous Solutions:I used Oracle Warehouse Builder (OWB) which is now at the end of its life. ODI is much more flexible and has the great advantage to be able to connect to a lot of different source or target technologies.Initial Setup:It was quite straightfoward.We did a migration for Oracle Warehouse Builder to Oracle Data Integrator 12c using the migration tool provided by Oracle. And I've to say I'm surprised to see a migration tool working so well!Implementation Team:In-houseDisclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2016-11-23
Rated 4 out of 5 by from 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.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.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2016-11-08
Rated 5 out of 5 by from A tool that can talk or learn how to talk, with any database or operating system in its own language. Valuable Features:Flexibility, ease of customization, extensive features, ease of deployment, and the ability to access to all kinds of different source system technologies. No need for extra hardware for transformation step. Easy to learn & develop.Oracle Data Integrator (ODI) can support any type of databases that has a jdbc driver in a native way. I have accessed and retrieve data from an Ingress database.Knowledge Module architecture helps you to build your data integration activities with less effort.You can switch to source, staging area or target to improve your querying performance. If you have to do a join from different source systems, you can decide which data to move to where and figure out the place for best output.Variables can help you to perform loops and conditional statements in packages for helping ETLImprovements to My Organization: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.Room for Improvement:They need to work on the multiuser development environment and include the ability to comply with different kinds of SDLCs.Use of Solution:I've been using it for more than 10 years, since Oracle acquired Sunopsis.Deployment Issues:There were no issues with the deployment.Stability Issues:I've experienced no issues with performance. Since sky is the limit, you can do what you want to do within ODI in several ways.Scalability Issues:It's been able to scale for our needs. ODI will fit your needs.Customer Service:10. I generally create a service request per year and they are being solved within a week.Technical Support:They're very efficient.Previous Solutions:We switched because of ODIs impressive increasement in development productivity.Initial Setup:It was straightforward and very easy. Almost the same as setup>next> next>next.Implementation Team:In-house.ROI:Worth every penny.Cost and Licensing Advice:There are various options in licensing, either per seat or per target core count. It depends how you want to use it.Other Solutions Considered:We also looked at Informatica Power Center, AbInitio, Business Objects Data Integrator (BODI), and SQL Server Integration Services (SSIS).Other Advice:If you want a robust, flexible solution with no extra hardware that is easy to learn, then ODI is the right product for you. ODI is a tool, that can talk or learn how to talk, with any database or operating system in its own language. This is the power of ODI.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:Partner
Date published: 2016-10-31
Rated 4 out of 5 by from It allows us to use many languages to develop and to integrate practically all the technologies of the Oracle suite as well as those from non-Oracle vendors. Valuable Features:It allows us to use many languages to develop and to integrate practically all the technologies of the Oracle suite as well as those from non-Oracle vendors.Improvements to My Organization:My organization develops solutions using all the Oracle EPM products, and ODI has helped us to integrate all the different technologies.Room for Improvement:I think that the product as an overall solution is good. I would only point out some minor bugs or glitches in the development interface (ODI studio), but I do not think that any of them are worthy to be reported here.Deployment Issues:There are some difficulties in moving a repository from an environment to a different one due to the internal numbering through which ODI references the objects belonging to a repository. This often causes troubles in the porting, and for this reason you always must pay attention during this operation.Stability Issues:I encountered many problems with the ODI web agent (service that actually executes all the integration tasks) in the 11g version, which was not stable. For this reason, I always suggest using the standalone agent instead of the web one, mostly due to the fact that they do not have significant differences.Scalability Issues:Scaling issues depend mostly on the tools that ODI uses to integrate the technologies. For example, if the number of records inside a table, which is the source of an integration task, increase greatly, the performance of the ODI integrating flows may degrade a lot. Their tuning, by the way, depends on the database (i.e. table partitioning, indexes or hints).Customer Service:I only experienced once the customer service provided by Oracle on ODI and was supported by capable and helpful people.Technical Support:The level of technical support is quite good. Apart from the first approach used to identify if the problem you are pointing out is a real issue or not, the second level support is really efficient and comprised of competent and clever people.Initial Setup:The initial setup is not really easy. To use ODI you must:* Install the ODI studio (client)* Create and configure a master and a work repository to develop on them, being sure that they can reach the database schemas you’ll work on (relational structures involved in the integration)* Install and configure an agent (if you need to communicate with more than a server and to schedule integration tasks), choosing properly where you need it and opening all the communication doors to allow it to reach all the parts of your architectureImplementation Team:I implemented it with an in-house team, since my company is a consultancy and also an Oracle partner.Even if ODI allows implementing a very smart solution with an high level of customization, I think that keeping the model of what you are developing as simple as possible is always the best choice. This is due to its future maintenance. Keep in mind that, even if you may be a very keen developer and you can propose the best and most parametric solution ever, if another (less expert) person inherits the responsibility of what you have developed, they may encounter difficulties in solving problems. For this reason, the easier you keep the complexity or technicalities of what you have created, the better it is.This is also valid for performance - one of the basic rules of the informatics development is “divide et impera”, which means that you should always try to create “objects” as small as you can to improve performance and to be able to identify quickly where a problem is.Cost and Licensing Advice:Being an ODI developer, I never had to pay for this product. I know that the pricing/licensing is not really low, but the product is really good.Other Solutions Considered:I tried many integration tools, both Oracle and other vendors. I think that ODI is one of the most complete and open solutions, since it can work with almost any technology and it gives you the ability to develop the same solution in a wide variety of ways depending on the one you prefer.Other Advice:Always keep in mind that ODI offers a huge number of solutions to any task you are developing. There is not a best practice in solving a problem; being able to identify the best solution for your particular problem is up to you and it may also be difficult to identify. This does not mean that the solution you have in mind is not correct.Always try to maintain an ordered environment, keeping only what you really need, and perhaps organizing the items in different projects or folders, or even different work repositories.Disclaimer: My company has a business relationship with this vendor other than being a customer:My company is an Oracle partner, and we develop with all Oracle business intelligence products.
Date published: 2016-10-31
Rated 4 out of 5 by from 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.
Date published: 2016-10-18
Rated 4 out of 5 by from 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.
Date published: 2016-10-17
Rated 3 out of 5 by from 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.
Date published: 2016-10-01
  • y_2017, m_2, d_20, h_23
  • bvseo_bulk, prod_bvrr, vn_bulk_0.0
  • cp_1, bvpage1
  • co_hasreviews, tv_0, tr_28
  • loc_en_US, sid_3153582, prod, sort_[SortEntry(order=SUBMISSION_TIME, direction=DESCENDING), SortEntry(order=FEATURED, direction=DESCENDING)]
  • clientName_cdwg
 
Adding to Cart...
2/22/2017 10:08:14 AM
^ 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.

Error!

Something went wrong.

Please try again later.