How to License Oracle Database Options (RAC, Multitenant, Partitioning) on AWS
Oracle Database options and management packs—such as Real Application Clusters (RAC), Multitenant, Partitioning, Advanced Security, Diagnostics Pack, and others—must be licensed separately on AWS, just as they are on-premises.
Here’s a clear breakdown of licensing rules, practical examples, and guidance for compliance when using Oracle Database options on AWS.
Read Oracle on AWS Licensing FAQs 2 of 4
1. Licensing Oracle Real Application Clusters (RAC) on AWS
Availability and Licensing:
- RAC is available only with Oracle Database Enterprise Edition (EE).
- On a per-processor basis, RAC must be licensed separately for every server node participating in the RAC cluster.
AWS Deployment Considerations:
- Amazon RDS does not support RAC. If you need RAC, you must deploy it manually on:
- Amazon EC2 instances (requires third-party shared storage or clustering solutions).
- VMware Cloud on AWS (VMC).
License Calculation Example:
- Scenario: 2-node RAC cluster, each EC2 node has eight vCPUs:
- Enterprise Edition licenses required per node:
- 8 vCPUs ÷ 2 = 4 Processor licenses per node (assuming hyper-threading is enabled).
- RAC licenses required per node:
- Additional 4 RAC Processor licenses per node (matching EE processor licenses).
- Enterprise Edition licenses required per node:
Summary Example:
- Total licenses for 2-node RAC cluster (8 vCPUs each node):
- 8 EE Processor licenses (4 per node)
- 8 RAC Processor licenses (4 per node)
2. Licensing Oracle Multitenant (Pluggable Databases) on AWS
Availability and Licensing:
- Multitenant is a separately licensed option for Oracle EE databases.
- Starting from Oracle Database 19c, you may run up to 3 Pluggable Databases (PDBs) within a single EE database without requiring a Multitenant license.
- More than 3 PDBs in one container database requires the Multitenant option license.
AWS Deployment Considerations:
- On Amazon EC2, you have full flexibility to use multiple PDBs—ensure licensing compliance if exceeding 3.
- On Amazon RDS for Oracle (standard), AWS currently allows only one user-created PDB per instance, so Multitenant licenses typically aren’t necessary unless AWS changes these restrictions.
- On RDS Custom or EC2, Multitenant licensing rules apply fully.
License Calculation Example:
- Scenario: Running an Oracle EE database on EC2 instance (with four processor licenses) containing 10 PDBs:
- Requires 4 Oracle EE Processor licenses for the instance itself.
- Additionally, it requires 4 Multitenant Processor licenses (matching EE processor count).
Summary Example:
- Licensing total for EC2 instance with 10 PDBs and eight vCPUs:
- 4 EE Processor licenses
- 4 Multitenant Processor licenses
3. Licensing Partitioning, Advanced Security, and Other Options
Oracle Database options like Partitioning, OLAP, Advanced Security, Advanced Compression, and Active Data Guard must also be separately licensed on AWS deployments, matching your EE licenses.
Key Points:
- Each Oracle database option is licensed per processor.
- No Oracle options are included in AWS’s License Included offerings (e.g., SE2 RDS).
- BYOL (Bring Your Own License) is required for these features.
License Calculation Example:
- Scenario: Using Oracle EE with Partitioning and Advanced Security on an EC2 instance with 8 vCPUs:
- EE licenses: 4 Processor licenses (8 ÷ 2).
- Partitioning licenses: 4 Processor licenses.
- Advanced Security licenses: 4 Processor licenses.
Summary Example:
- Total licenses required (8 vCPU EC2 instance):
- 4 EE Processor licenses
- 4 Partitioning Processor licenses
- 4 Advanced Security Processor licenses
4. Licensing Oracle Management Packs (Diagnostics and Tuning) on AWS
Oracle Management Packs, such as Diagnostics Pack and Tuning Pack, are licensed separately and often inadvertently enabled by DBAs (e.g., generating AWR reports).
Licensing Rules:
- Each Management Pack is licensed per processor, matching EE licenses.
- Using Automatic Workload Repository (AWR), Performance Hub, or related features triggers licensing requirements.
AWS Deployment Considerations:
- On EC2, these features are freely available, but licensing is required once used.
- On standard RDS, AWS typically restricts usage unless explicitly declared with BYOL.
License Calculation Example:
- Scenario: EC2-based Oracle EE database with Diagnostics and Tuning Packs enabled, running on four processor licenses:
- EE licenses: 4 Processor licenses.
- Diagnostics Pack licenses: 4 Processor licenses.
- Tuning Pack licenses: 4 Processor licenses.
Summary Example:
- Total required licenses:
- 4 EE Processor licenses
- 4 Diagnostics Pack licenses
- 4 Tuning Pack licenses
5. Tracking and Ensuring Compliance on AWS
AWS does not automatically enforce Oracle option licensing—compliance responsibility remains yours.
Best Practices:
- Regularly run Oracle’s built-in
DBA_FEATURE_USAGE_STATISTICSqueries to check for usage of licensed features. - Document license allocations internally.
- Disable any Oracle database options you have not explicitly licensed.
Practical Example:
- Auditors often inspect
DBA_FEATURE_USAGE_STATISTICS:- If “Partitioning” is listed as “used,” ensure you have documented licenses matching the processor count.
6. No Special Cloud Pricing for Oracle Options
Oracle database options do not receive special or discounted cloud pricing. Pricing and licensing requirements remain identical to traditional on-premises deployments.
- AWS deployments follow the standard Oracle Processor-based pricing model.
- Oracle offers no discounts or cloud-specific license bundles for AWS.
Example:
- The partitioning option costs the same per processor, whether on-prem or AWS EC2.
Practical Licensing Summary Table for AWS Oracle Database Options
| Oracle Option / Pack | Required License Metric | Example AWS Scenario (8 vCPUs) | Licenses Required |
|---|---|---|---|
| Real Application Clusters | Processor per node | 2-node RAC cluster (each 8 vCPUs) | 8 RAC Processor licenses (4 per node) |
| Multitenant | Processors per instance | 1 instance (8 vCPUs) with 10 PDBs | 4 Multitenant Processor licenses |
| Partitioning | Processors per instance | 1 instance (8 vCPUs), Partitioning enabled | 4 Partitioning Processor licenses |
| Advanced Security | Processors per instance | 1 instance (8 vCPUs), Advanced Security used | 4 Advanced Security Processor licenses |
| Diagnostics/Tuning Packs | 2-node RAC cluster (each eight vCPUs) | 1 instance (8 vCPUs), Packs used | 4 Diagnostics Pack licenses, 4 Tuning Pack licenses |
Licensing Checklist for Oracle Database Options on AWS
✅ License each Oracle option or pack separately per processor.
✅ Regularly audit database feature usage for compliance.
✅ Document Oracle license allocations internally for audit readiness.
✅ Disable unused or unlicensed Oracle features.
✅ Consider licensing implications before enabling advanced Oracle features.
Read Oracle Real Application Clusters (RAC) on AWS: Licensing.
Common Misunderstandings Corrected
- Misconception: “AWS provides Oracle database options included in RDS License Included.”
- Reality: The RDS License covers the SE2 database only, with no EE options.
- Misconception: “Oracle options licensing is different on AWS.”
- Reality: Licensing and pricing rules are identical to on-premises.
- Misconception: “You don’t need to license database packs unless they are explicitly installed.”
- Reality: If packs like Diagnostics or Tuning are used (even inadvertently), licenses are required.
Conclusion: Licensing Oracle Database Options on AWS
Oracle Database options and management packs must always be licensed separately on AWS, just as on-premises. You must carefully monitor and document their usage, as AWS does not automatically manage compliance. Understanding these licensing rules and keeping accurate records ensures your Oracle deployments on AWS remain compliant and cost-effective.
