--- sourceDocument: Xanadu IT Asset Management sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-asset-management Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu IT Asset Management ft:clusterId : - itam bundleId : - itam workflow : - Technology --- # Oracle Database licensing in multitenant architectures # Oracle Database licensing in multitenant architectures {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 9 minutes to read The Software Asset Management application supports licensing rules for Oracle databases in multitenant architectures. The Oracle multitenant architecture simplifies database management by enabling you to consolidate multiple pluggable databases (PDBs) into a single container database (CDB). With a CDB, you can track, provision, clone, manage resources for, and upgrade multiple PDBs simultaneously. This multitenant architecture is supported on Oracle Database version 12c Release 1 (12.1) and later. To run an Oracle database in a multitenant architecture, you must purchase and manage licenses for both Oracle Database and the Oracle Multitenant option. In most cases, Oracle Multitenant option licenses must be purchased and managed separately from Oracle Database licenses. However, Oracle Database Cloud Service Enterprise Edition - High Performance (DBCS EE-HP), Oracle Database Cloud Service Enterprise Edition - Extreme Performance (DBCS EE-EP), and Oracle Database Exadata Cloud Service (ExaCS) do not require a separate license for the Oracle Multitenant option, as it is already included in the database license. For more information on Oracle Database licensing, see [Software Asset Management publisher pack for Oracle](https://www.servicenow.com/docs/VspujOnQ80pYLclYZgahNQ "Use the Software Asset Management publisher pack for Oracle to track and optimize licensing for your Oracle products."). ## Oracle Multitenant option licensing {#oracle-licensing-multitenant-architectures__section_kns_c5t_2rb} The Oracle Multitenant option supports both the Named User Plus and Per Processor license metrics. The Named User Plus license metric licenses all users and physical devices that access a user-created PDB. The Per Processor license metric licenses the processor cores on all physical hosts that are running a user-created PDB. For more information on these license metrics, see [Oracle license metrics](https://www.servicenow.com/docs/VspujOnQ80pYLclYZgahNQ#oracle-publisher-pack__section_q2j_3dn_qpb). Important: Oracle Multitenant option licensing accounts for user-created PDBs only. It does not account for proxy PDBs or seed PDBs. You can determine whether Oracle Multitenant option licensing is required for your database deployment based on the following criteria: * The Oracle Database version and edition of your PDBs and CDBs. * The number of user-created PDBs within each database instance that is running on the database installation. {#oracle-licensing-multitenant-architectures__ul_btl_cfy_drb} {#oracle-licensing-multitenant-architectures__table_ck2_wy5_vrb__entry__3} | Oracle Database version | Oracle Database edition | Licensing requirement | |-|-|-| | 12c Release 1 (12.1) | Oracle Database Standard Edition (SE) | The Oracle Multitenant option is not supported. | | 12c Release 1 (12.1) | Oracle Database Standard Edition One (SE1) | The Oracle Multitenant option is not supported. | | 12c Release 1 (12.1) | Oracle Database Standard Edition 2 (SE2) | The Oracle Multitenant option is not supported. | | 12c Release 1 (12.1) | Oracle Database Enterprise Edition (EE) | * If every database instance contains only one user-created PDB each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than one user-created PDB, licensing is required using either the Named User Plus or Per Processor license metric. Important: This version and edition of Oracle Database supports up to 252 user-created PDBs per database instance. If a database instance contains more than 252 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_dk2_wy5_vrb} | | 12c Release 2 (12.2) and 18c | Oracle Database Enterprise Edition (EE) | * If every database instance contains only one user-created PDB each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than one user-created PDB, licensing is required using either the Named User Plus or Per Processor license metric. Important: This version and edition of Oracle Database supports up to 252 user-created PDBs per database instance. If a database instance contains more than 252 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_ek2_wy5_vrb} | | 12c Release 2 (12.2) and 18c | Oracle Database Standard Edition 2 (SE2) | The Oracle Multitenant option is supported only in deployments where every database instance contains one user-created PDB each. However, licensing is not required since the Oracle Multitenant option is not in use. | | 12c Release 2 (12.2) and 18c | Oracle Database Cloud Service Enterprise Edition - High Performance (DBCS EE-HP) | * If every database instance contains one user-created PDB each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than one user-created PDB, the Oracle Multitenant option is in use. However, separate licensing is not required for this option since it is already included in the Oracle Database license. Important: These versions and editions of Oracle Database support up to 4,096 user-created PDBs per database instance. If a database instance contains more than 4,096 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_gk2_wy5_vrb} | | 12c Release 2 (12.2) and 18c | Oracle Database Cloud Service Enterprise Edition - Extreme Performance (DBCS EE-EP) | * If every database instance contains one user-created PDB each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than one user-created PDB, the Oracle Multitenant option is in use. However, separate licensing is not required for this option since it is already included in the Oracle Database license. Important: These versions and editions of Oracle Database support up to 4,096 user-created PDBs per database instance. If a database instance contains more than 4,096 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_gk2_wy5_vrb} | | 12c Release 2 (12.2) and 18c | Oracle Database Exadata Cloud Service (ExaCS) | * If every database instance contains one user-created PDB each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than one user-created PDB, the Oracle Multitenant option is in use. However, separate licensing is not required for this option since it is already included in the Oracle Database license. Important: These versions and editions of Oracle Database support up to 4,096 user-created PDBs per database instance. If a database instance contains more than 4,096 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_gk2_wy5_vrb} | | 19c and later | Oracle Database Enterprise Edition (EE) | * If every database instance contains three or less user-created PDBs each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than three user-created PDBs, licensing is required using either the Named User Plus or Per Processor license metric. Important: This version and edition of Oracle Database supports up to 252 user-created PDBs per database instance. If a database instance contains more than 252 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_hk2_wy5_vrb} | | 19c and later | Oracle Database Standard Edition 2 (SE2) | The Oracle Multitenant option is supported only in deployments where every database instance contains three or less user-created PDBs each. However, licensing is not required since the Oracle Multitenant option is not in use. | | 19c and later | Oracle Database Cloud Service Enterprise Edition - High Performance (DBCS EE-HP) | * If every database instance contains three or less user-created PDBs each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than three user-created PDBs, the Oracle Multitenant option is in use. However, separate licensing is not required for this option since it is already included in the Oracle Database license. Important: These versions and editions of Oracle Database support up to 4,096 user-created PDBs per database instance. If a database instance contains more than 4,096 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_jk2_wy5_vrb} | | 19c and later | Oracle Database Cloud Service Enterprise Edition - Extreme Performance (DBCS EE-EP) | * If every database instance contains three or less user-created PDBs each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than three user-created PDBs, the Oracle Multitenant option is in use. However, separate licensing is not required for this option since it is already included in the Oracle Database license. Important: These versions and editions of Oracle Database support up to 4,096 user-created PDBs per database instance. If a database instance contains more than 4,096 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_jk2_wy5_vrb} | | 19c and later | Oracle Database Exadata Cloud Service (ExaCS) | * If every database instance contains three or less user-created PDBs each, licensing is not required since the Oracle Multitenant option is not in use. * If any database instance contains more than three user-created PDBs, the Oracle Multitenant option is in use. However, separate licensing is not required for this option since it is already included in the Oracle Database license. Important: These versions and editions of Oracle Database support up to 4,096 user-created PDBs per database instance. If a database instance contains more than 4,096 user-created PDBs, Software Asset Management creates removal candidates for the additional PDBs. You must remove the additional PDBs to maintain compliance. {#oracle-licensing-multitenant-architectures__ul_jk2_wy5_vrb} | [Table 1. Oracle Multitenant option licensing requirements] {#oracle-licensing-multitenant-architectures__table_ck2_wy5_vrb} * **[Oracle Multitenant option use cases](https://www.servicenow.com/docs/EWYt9HBAwfkMOJ06wDS1VA)** You can view the following use cases to better understand licensing requirements for the Oracle Multitenant option.