We performed a comparison between Oracle Data Integrator (ODI) and Qlik Replicate based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases."
"All ETL code is stored in repositories in underlying database schemas. The number of users can access and work on the same solution using a client tool. So distributed teams can work on this tool in an efficient manner."
"The tool improved our data integration workflow primarily due to its compatibility with Oracle. Its integration makes it very convenient for analytics. Its most valuable feature is robust extended capability. The solution's debugging capabilities are good."
"The most valuable feature that we use is the Knowledge Modules."
"It's scalable."
"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."
"It is an ETL tool, which does the extract, transform, and load."
"Great with replicating and updating records."
"We use Qlik Replicate to change data capture of databases in production environments."
"Support has been great."
"A valuable feature of Qlik Replicate is that you do not need ETL. It's easy to use—you choose two systems and it automatically replicates them. Even if there is no CDC available, if you insert it and update it, and there is nothing to find out, then you can use Qlik Replicate. It's a good product."
"The most useful functions of Qlik Replicate are the data manipulation to transformations."
"From a technical perspective, this is an excellent product."
"Low-priced reporting and analytics solution, with good scalability and stability. It has on-premises and cloud versions that are cohesive and can integrate well."
"It's very user-friendly when it comes to settings and configuration. It also offers very detailed logging about warnings and errors."
"If there was an add-on tool to hide the performance issues and solve them for me, then I might be interested in that as it would provide me value."
"The initial setup is a bit complex compared to other tools."
"It has been very good. Just recently, I've faced an issue, but I solved it somehow. While integrating with a file, I faced an issue where I wanted output files, and I had used the text field limited quotations, but at the end of the file, there was a line breakage for the last column. So, we just removed the text field because it was not working correctly for us."
"The resource management aspect of the solution could be improved."
"The performance of the user interface is in need of improvement."
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"It needs easier security."
"Stability could be improved because some operators have issues."
"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."
"This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved."
"In various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement."
"Support for this product is not great. It needs to be improved."
"When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating."
"We would like to see more details in messages about errors with the system."
"We'd like better connectivity."
"Support-wise, this solution is in need of improvement."
Oracle Data Integrator (ODI) is ranked 4th in Data Integration with 67 reviews while Qlik Replicate is ranked 16th in Data Integration with 13 reviews. Oracle Data Integrator (ODI) is rated 8.2, while Qlik Replicate is rated 8.2. The top reviewer of Oracle Data Integrator (ODI) writes "Straightforward to implement, scalable, and has good stability and documentation, but technical support could still be improved". On the other hand, the top reviewer of Qlik Replicate writes " Performs well with batch-wise data applications but some features can also be overly dependent on each other". Oracle Data Integrator (ODI) is most compared with Oracle Integration Cloud Service, Informatica PowerCenter, SSIS, Azure Data Factory and Oracle GoldenGate, whereas Qlik Replicate is most compared with Oracle GoldenGate, AWS Database Migration Service, Qlik Compose, Azure Data Factory and Fivetran. See our Oracle Data Integrator (ODI) vs. Qlik Replicate report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.