Multitenant has a container database with many pluggable databases. A great feature is that you can upgrade the container to a more recent version and all the pluggable databases are automatically upgraded to that version. Previously it would have required an upgrade for each database. The second great feature is the clone which enables you to get the clone of pluggable databases with one command, as opposed to copying data from one place to another. 

Oracle Multitenant has a filter for private databases. 

The best thing about Oracle Multitenant for us, as a software development company serving many clients, is its ability to consolidate multiple databases into one engine. This simplifies management and allows us to easily handle different client versions on our servers by creating copies of their databases.

I do like the security features and data recovery for features that were enabled there. With the right configurations, you can maintain an environment without retaining the risk of losing any kind of data. 

There's also a point in time recovery, et cetera. This is quite useful. 

The initial setup is simple. 

It is a stable product.

You can scale the solution as needed. 

It is very feature-rich.

1. The ability to create multiple databases without using any additional memory and CPU, and reallocating resources among these databases as needed, dynamically, without restarting.

2. The marriage of snapshot technology with this alleviating the need for additional storage for the containers.

It's about consolidation. They are trying to solve all the issues. Oracle has many solutions for managing resources. For example, if you have many applications to maintain, some applications share the same database. They need to restart, which will impact the other applications. You will have to stop all the services and that adds to downtime.

To solve this issue, Oracle Multitenant provides one container database. It is set up with many databases within each other as in a schema database. You will make each application connected to the pluggable database.

The database becomes pluggable. Inside this container is called a pluggable database and each application contains this pluggable database inside multitenant. We can then share resources like control files, memory, etc. This lets you stop and start each application without impacting the others. This resource sharing is the most valuable feature

If you would like to do this with the older version or another system, you would have to install many databases and each database will get a resource. Then you have to buy resources for the license, CPU, server, etc.

This is the main feature they use this solution for. Of course, if you get a cloud database service, they may not give you a dedicated database. If so, they will provide a pluggable one for part of the container like virtualization or clone. You can use this solution in that way also.

According to my point of view, this is the main feature with 12c compared to 11. It is called 12c for the cloud since they are preparing to move more to the cloud.

In the cloud, you're sharing resources. Not every database has a high load, so they distribute resources from one controller to this pluggable database.

They are sharing resources because there are usually wasted resources otherwise. There are companies that check the vitalization of your server, memory, hardware, and infrastructure. You will find that 70% or 80% of your resources are wasted.

The cloning features are outstanding. It’s easy to clone an existing database in the same CDB into another CDB running on-premise or even to a CDB running in a private or public cloud. This opens new doors database consolidation with an easy deployment or change of the underlying hardware.

It's very helpful for cloning. The pluggable databases and everything works super easy, because we clone the databases every week. This saves time and effort.

I have found that its top-down approach from container database to the pluggable database is seamless, logical and gets aligned to business rules pretty easily. This is very valuable for our business.

The plug/unplug is the great feature, that doesn't even need the Multitenant option. Oracle introduced Transportable Tablespaces in 1999 to move physically the user data, but metadata was still imported though Data Pump. Pluggable databases go beyond that; metadata is also transported because each PDB has its own SYSTEM tablespace. This is the faster data movement and allows copy-on-write snapshots.

The feature that I like about Multitenant is the ease - it is very easy for my team to run the database.

The most valuable features are the speed and ease of use.

This solution has more features, for example in security, than competing products.

Maintaining databases is a valuable feature for us.