1. Home
  2. Relational Databases
  3. Oracle Database Reviews
  4. User Review of Oracle Database
Review
Updated April 29, 2021

Review

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Oracle Database

Oracle 12c is used to support the shopping website of the organization, it's very robust, high performing and THE database is scalable to the needs of increasing traffic on the site. It addressed especially the problem with consolidating databases and scaling, much needed performance of apps using Oracle database.
  • Multitenant architecture has reduced the DB foot print and maintenance.
  • Refreshing test database from production has become affordable and manageable.
  • Restoring and recovering tables with Rman has become easy with 12c.
  • Like MySQL Oracle also should provide a way to manage both unstructured and structured Data in same DB.
  • More free training through OTN (self study videos) about 12c performance and how to adapt to it.
  • Plan stability without adapting to use SPM when upgrading to newer versions. SPM has caused problems like taking up too much memory in the DB server when implementing it to overcome the shortcomings of upgrade with optimizer behavior altering the performance. In a way a more adaptable approach would be beneficial for DBAs for upgrade not compromising performance which I think is one of the biggest challenges upgrading .
  • Reduced Oracle licensing costs adapting to multi-tenant.
  • Reduce hardware foot print.
  • DB Performance was not stable with upgrade unless the optimizer was switched back to past version even after upgrade.
Exadata is expensive and we decided to switch to 12c for the sake of consolidating and keep up with Oracles initiative to move towards cloud. Maybe in the future.
With multi-tenant architecture managing multiple databases under one roof has become easier. Cloning and patching has also become easier with 12c. On the other hand performance management post-upgrade has been an issue, choosing optimizer parameter to 12.1.0.2 post upgrade has become even tougher as plans kept changing and implementing SPM took up more memory. Looking for a better way to manage performance post-upgrade in future from Oracle.

Also running datapatch post-patching on a busy DB server is a nightmare as sometimes it would never complete and also unplugging and plugging DBs across clusters with different patch sets is a pain too.