Multitenant Licensing Model in 12.1 and Beyond: A Core-Based Approach

Despite its innovative logical architecture, Multitenant licensing in versions beyond 12.1 aligns with previous models. Software licenses, encompassing database and additional options, are determined by the number of CPU cores. This holds true for Named User Plus (NUP) licensing as well.

Let's illustrate: an 8-core server (two Intel processors with four cores each) necessitates the procurement of licenses for four cores (8 * 0.5, where 0.5 is the Intel core licensing factor). This encompasses database, Multitenant, and other options like partitioning.

Consider a scenario with one Container Database (CDB) and three Pluggable Databases (PDBs). PDB1 utilizes partitioning, PDB2 utilizes only Automatic Storage Optimization (ASO), and PDB3 uses no additional options. Regardless of individual PDB usage, licenses must be acquired for the database, Multitenant feature, ASO feature, and partitioning for four cores.

In the case of NUP licensing, a minimum of 100 NUPs (4 cores * 25 NUPs per core) or the actual number of users, whichever is greater, is required.

Essentially, license calculation hinges on the total number of server cores and the utilization of any option within the CDB, irrespective of specific PDB usage. All purchased options are accessible to every PDB within the CDB.