We performed a comparison between Oracle OBIEE and Pentaho Business Analytics based on real PeerSpot user reviews.
Find out in this report how the two Reporting solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The main features of this solution are that it is easy to use, intuitive, and user-friendly. When I retrieve the data from the database it is in a very raw form, then when I use the Oracle Report Builder it has advanced intelligence features to allow me to view and make changes to the data easily."
"Scalability-wise, I rate the solution a nine out of ten...The solution's initial setup was straightforward."
"The technical support services are good."
"The solution is easy to use and very flexible."
"The most valuable feature is the openness of the solution. It helps us integrate some of our clients."
"We can see almost-real-time performance in our operations. When there is a problem, it is easy to escalate it to top management and the time for management to make a decision about it is much shorter than it would be using a manual process."
"The most valuable feature is the reporting."
"I think having the conformed structures makes it a lot easier for end users and pulling reports together."
"Pentaho is an analytics platform that can be used when an organization has a lot of big data storage systems already installed and needs to manage and analyze that data. It has a specific use case for unstructured data, such as documents, and needs to be able to search and analyze it."
"The initial setup is pretty straightforward."
"The most valuable feature of Pentaho is the Tableau report."
"Easy to use components to create the job."
"We were able to install it without any assistance from tech support."
"Pentaho Business Analytics' best features include the ease of developing data flows and the wide range of options to connect to databases, including those on the cloud."
"I use the BI Server, CDE Dashboards, Saiku, and Kettle, because these tools are very good and highly experienced."
"Even though we have a feature to enable the physical query to be seen in the log, in case of any issues, it is challenging to debug and see or identify where is the issue. For example, we designed the OBIEE repository and deployed it into the server, and we are now accessing and creating a report. For some reason, if the report is not working as expected, it is very difficult to identify the issue. We have a feature to see the physical query that is being generated in the central OBIEE server. I feel that this feature should have been available at the repository level so that while designing the repository, we can select the presentation columns and the query it is going to create. This will avoid the additional task of deploying a feature into the server and then testing the report. It will also make the implementation process friendly if, while designing the repository, we can see: How is a feature working? Are any of the presentation columns selected? How is the query being generated? Which query is being generated? Are any joints used? What kind of joints are used? Having this kind of information will make Oracle OBIEE more powerful and developer-friendly."
"The pricing of the solution should be bettered."
"The documentation in Oracle OBIEE can be more user-friendly."
"The platform's data visualization features need improvement."
"The performance could improve and in a future release, they could provide more virtualization options."
"The functionality to customize and modify reports has been removed, and it would be beneficial to reinstall it, as it allows greater customization and flexibility in creating reports."
"There are a lot of aspects of Oracle OBIEE that are exceptionally complicated, make things unnecessarily difficult for everyone who uses it. In terms of the integrations, Oracle needs to improve a little more, but I believe that they have tried to capture all those issues. The issues we are facing in the Oracle OBIEE 12C versions, in the Oracle Analytical Server Center or Analytical Cloud versions, Oracle has managed to overcome the challenges."
"The platform's interface needs improvement."
"Deployment is not simple. It is not simple because we are dealing with a lot of data; we are dealing with a lot of storage. So, it's not a simple process."
"The repository should be improved."
"Logging capability is needed."
"Pentaho Business Analytics' user interface is outdated."
"Version control would be a good addition."
"Another concern is that Pentaho is not customizable or interactive."
"Pentaho, at the general level, should greatly improve the easy construction of its dashboards and easy integration of information from different sources without technical user intervention."
"We did not achieve the ROI. The work delivered to users had lesser value than the subscription cost."
Oracle OBIEE is ranked 3rd in Reporting with 154 reviews while Pentaho Business Analytics is ranked 16th in Reporting with 42 reviews. Oracle OBIEE is rated 7.8, while Pentaho Business Analytics is rated 8.0. The top reviewer of Oracle OBIEE writes "A solution that is easily accessible, scalable and requires a straightforward initial setup process to get started". On the other hand, the top reviewer of Pentaho Business Analytics writes "Flexible, easy to understand, and simple to set up". Oracle OBIEE is most compared with Microsoft Power BI, SAP BusinessObjects Business Intelligence Platform, IBM Cognos, Tableau and Oracle Analytics Cloud, whereas Pentaho Business Analytics is most compared with Microsoft Power BI, Databricks, Microsoft SQL Server Reporting Services, SAP Crystal Reports and Qlik Sense. See our Oracle OBIEE vs. Pentaho Business Analytics report.
See our list of best Reporting vendors and best BI (Business Intelligence) Tools vendors.
We monitor all Reporting 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.