Oracle Database

It's the best one in terms of Relational Database with the support to indexing, maintaining relations between the tables, etc.

Faster performance in fetching results, especially when running complex queries with multiple tables.

There's no easy way to Store JSON objects in the DB. We had to do some workarounds.

We need a little more detailed explanations for the exceptions or errors thrown. For example, if it reaches a session limit while fetching a connection, it's better to throw the count in there that X of X are currently in use, etc.

Provide edge technology.

Customer support is sometimes bad and if the ticket is not high priority It could take a lot of time to be attended to.

Disaster recovery solutions.

Replication solutions.

Performance, Tuning, and Troubleshooting should be simplified and all the data needed for troubleshooting should be in one easy to access place.

Faster data management.

Better options for automating DBA functions.

Cloning and backup.

Security and encryption should be simplified.

Customer Support response time should be better.

The OEM is too slow.

Complex query - this is true for relational databases but more so for Oracle due to its robust implementation of ANSI-SQL and the relational paradigm for data management.

The various options available within the database are second to none. No one has the same level of partitioning as Oracle does for example.

Even though some other databases have similar capabilities no one can match Oracle RAC to any real degree.

Oracle is slowly moving this was but allowing the database to consume more data repositories and query them all from a single interface would be a great enhancement. Oracle Big SQL has this but is a paid option that sits outside of the database and has access to a small number of repositories (HDFS for example).

Make licensing more easily consumable and client-friendly. This is the biggest bone of contention that is pushing customers from what is a truly great product.

Advanced Index Compression.

Approximate Count Distinct.

In-Memory Column Store.

ConfigToolAllCommands

DBMS_DEBUG Package

Sharding

Stability.

Easy to use.

Capabilities.

There are other products that are easier to configure.

Price.

Performance

Security

Stability

OLTP transactions are so very fast. We have 5,000 concurrent users and results are shown so fast.

Compatible with different application vendors and require less configuration. We are using SharePoint, Sales Online, and other applications.

Data replication with ADG is very powerfull and requires less latency. Currently, we have real-time replication without much interference.

Oracle should have a single implementation method for all platforms regardless of different operating systems.

Migration tool for other databases should be quick, without a user interface.

Data cleansing and data validation tools needed.

Pluggable Database structure

Restoring a table easily through RMAN

Multiple indexes on a single column

Temporary UNDO

Columnar tables.

Compression after update on HCC (Hybrid Columnar Compression) tables automatically.

More analytical functions.

More functions in data mining, data science, and machine learning algorithms.

Fast database to run and easy to use

Reliable and consistent for implementation and no critical updates

The security and encryption options

SQL function with support for C library

Data and storage partition

Migration process

Upgrade of new releases

Core factor for enterprise edition with HW products

VMware clusters to licence

Support JSON

Oracle DB can handle large amounts of data without any issues. For example, Salesforce processes billions of records every hour in the cloud. Their underlying database is Oracle.

Oracle DB provides industrial-strength support for online backup and recovery.

Another advantage of Oracle DB is its reliability. Oracle DB delivers excellent performance when challenged with demanding tasks. The ACID test, which is an important tool used to ensure the integrity of data stored, was easily passed by the Oracle database.

Oracle database is very expensive. It can cost 9-10x as much as Microsoft SQL Server.

Oracle database is an extremely complex engine. Expert knowledge is required to design a database and architecture.

You need an expert to maintain an Oracle Database. Day to day maintenance itself require a skilled resource.

The need for any other software is not there.

There are many features in the Oracle 12c database.

Cost is the main factor here which needs improvement. Some clients requirements can be done only with the extra features this product provides but cost comes in between so ultimately we have to use MySQL for that.

Technical support also needs improvement.

Accessibility. It's very easy to grant end-user access to the data. Oracle has done a fantastic job of providing developer-friendly tools. SQL Developer is a top-notch product, that is completely free for developers. It allows people to easily and clearly query and update data.

Education. There is a definite career path laid out by Oracle to develop skills to develop, administer, or use this database, and its peripheral suite of products. Aside from what Oracle itself provides, the user community does really well to encourage knowledge sharing. The user groups are fantastic.

Speed. From querying to load and unload utilities, Oracle can perform to your expectations. We use the diagnostic tuning pack to help aid with specific query tuning. As good as the optimizer is, it sometimes still requires a DBA to hint it in the right direction. Adding optimizer hints to SQL is a life-saver.

Security. I feel that this is a secure, mature product that stays abreast of the climate with frequent patches. When vulnerabilities are discovered, we are alerted promptly by Oracle.

Complexity. The trade-off for the excellent performance and many features is a complex structure. We have 3 different types of DBAs to support various aspects of the system. One focused on application performance and design, another on maintenance and security, and a third on alerting and patches. Each is a full-time job.

The push to cloud services is nauseating. It seems like a major focus for Oracle, and something our shop has little interest in.

I've never felt that we get our money's worth with support. This is true with almost all software, but I would expect better from Oracle.

RAC architecture works as promised, but adds an even greater level of complexity to your system. There are things from an administration standpoint that are not yet consolidated across RAC nodes. For example, if you are looking for a specific user session and run 3 active nodes, you have a search 3 places for it. There should be utilities to traverse all RAC nodes for you. It's 2019. I'd like to see less development for cloud technology and more in that area.

The standby database is the same. Works as advised, but adds complexity and extra administration.

OEM 12C allows cloud monitoring. We can install OEM on one server and monitor all my databases (11G R2 and above) hence I need to manage just one link. It also allows heterogeneous database monitoring, host monitoring, out offline patching.

We do not have an option to recover tables from Rman backup prior to 12C hence we had to be only depending on logical backups.

But using 12C database we can recover tables as well.

When we look for availability RAC comes to our mind and Oracle Database 12C came up with new features related to ASM and RAC like Flex cluster and Flex ASM using which if at all ASM instance goes down in a RAC node it can make use of asm that is running in other node hence ensuring availability. In Flex cluster we need to have Flex asm and the leaf nodes. There will be no database/ASM instances running in leaf nodes but only the application servers. The incoming connection come to leaf node and then to the actual hub server. Leaf nodes reduce the cost as there is no need for internode communication between leaf nodes. The internode connection should be there within hub nodes.

I don't see any such disadvantages but the multitenant structure seems bit complicated and same should be presented in simpler manner

Great SQL client that allows for advanced querying.

Extensive support for stored procedures, functions, materialized views, windowing functions, and other useful SQL operations.

Stable. Oracle Database has been around for many years and has a large developer community.

Expensive. There are several free alternatives (Postgres, MySQL).

More difficult to install and setup than other alternatives (ie: MySQL).

Difficult to support and administer (ie: backups).

Oracle databases are ideal for maintaining data (insert, update, delete).

The SQL (Structured Query Language) and PL/SQL (Procedural Language / Structured Query Language) languages are very powerful ways to interact with Oracle databases and retrieve data.

The databases have administrator tools that make maintenance of the databases simple.

Some error messages tend to be a bit ambiguous.

Although Oracle is a relational database, they rules are not strictly enforced. I suppose this allows for more flexibility and customization, but it would be nice to have inherent foreign keys, etc.

There have been times where updating the database has resulted in some functionality (i.e. keywords, tuning methods, etc.) to be deprecated which has required my teams to rewrite code.

Robustness, the way it handles relational databases as well as other services required for a fault-tolerant database environment.

Consistency, the reliability of the fact that data is being consistently stored in each transaction.

Ease of configuration.

Integration with third-party applications.

It is pretty expensive, it makes more sense to buy this product if you have a lot of transactions per second.

Integration with Microsoft technologies is not as good as Microsoft SQL servers.

Other then these, I cannot think of any other areas that require improvements.

It is robust and scalable.

Very easy to handle large quantities of data.

Different users can interact with Oracle Database using various tools and applications and thus it can run on a wide range of platforms.

It should be easy to use. If you haven't worked on any tool like this, then yes you may need assistance to use this.

The licensing cost is bit on a higher side.

Customization can be improved.

We have databases in two data centers geographically located in different places in our region. The Oracle 12c Data Guard feature makes sure the data instance is synchronized in a near real-time manner from the primary instance to the standby instance, across the data centers to provide data center level failure resilience.

Database instance's high availability is guaranteed by the RAC feature, which also helps us scale up resources like servers, CPU and memory.

Performance tuning toolset provided by Oracle Database is quite handy.

The security feature is extremely important for our company, and we are quite happy about what is offered by Oracle Database.

Oracle DB doesn't work very well for dealing with a large amount of time series based data rows performance wise.

The traditional primary/standby mode of data guard architecture, causing half of the resources (Stand-By side) to be idle most of the time and become a wasted investment. In the future, the near real-time data sync should be made available on the standby side and should allow the read-only operation, so at least business can use the resources for data analytic purposes. That will be great

When traditional relational database architecture is challenged by the NoSQL Technics, in most of the case, the business or the end user is not looking for some "Oracle DB" replacement solution, instead, they are seeking a "hybrid" solution. As they get used to the Oracle environment and they like the ACID operation, what they are looking for the flexibility features that are provided by pure NoSQL products (like variable columns for different rows in the same table etc). Oracle has some improvements like security file on BLOB, but if Oracle can make more improvements aiming in this direction, that can bring more added value and retain a lot of old users

For some use cases, we noticed that database performance deteriorating if we have relatively high active connection sessions

The Oracle optimizer is getting smarter in every Oracle release. In 12c, the adaptive query optimization features helped a lot to improve query performance.

In 12c, we can restore a single table from RMAN backups - it's a very useful and time-saving feature when we need to recover a particular software module.

I see the scope of improving the optimizer capabilities to automatically handle run-away queries better, meaning, if a SQL suddenly comes up with a bad execution plan, the database needs to be able to handle it smoothly, rather than affecting other SQL.

Parallel Querying

Optimizing the queries during execution

Better performance

CDB & PDB technologies

Gather stats collection

Parallel querying

Accessing the data from physical disks

High reliability. Zero hiccups!

Possibly the best data security money can buy

Allows single table restoration from backups (this feature is brilliant)

The handler for bad queries could be better

Compared to previous versions, Oracle 12c is a pretty heavy setup. If your business is considering an upgrade, ensure that you perform a pre-check of your systems' ability to work well with the requirements of 12c.

Highly Secure

Scalable

Oracle Database 12c has the new multitenant feature - where companies can consolidate multiple databases from different servers under a single container database thereby helping with cost cutting as well

Robust Backup and Recovery technology

Database Performance and Tuning Requires skills

Managing Social Media types of data

Always there are bugs and involves heavy maintenance

Pluggable databases, as mentioned

Temporary undo

Invisible columns indexes

PGA limit

Identity columns

Multiple indexes on a single column

Cost

Optimizer could be better. Many times generating stats on individual objects throws the optimizer off . Rather than utilizing the older better stats it uses the newer bad stats for specific queries

Patching without taking down db.

Ways to change parameters and force them to stay without taking down db

OEM should be included in cost.

Hard to learn as a newbie.

Very expensive for startups