Oracle Database 23ai Licensing

Oracle Database 23ai: What It Is and Why It Matters for Licensing

Oracle Database 23ai was formally released in May 2024, initially on Oracle Cloud Infrastructure (OCI) and Oracle Exadata, with general on-premises availability for non-Exadata hardware still pending as of early 2026. The "ai" designation reflects Oracle's repositioning of the database as a native platform for artificial intelligence workloads, with AI Vector Search, Select AI, JSON Relational Duality, and more than 300 other features shipped in the release.

From a licensing perspective, 23ai introduces no new top-level metric or completely new edition. The same processor and Named User Plus (NUP) framework applies. The same edition hierarchy — Enterprise Edition, Standard Edition 2, and a free edition — is preserved. What has changed is the capability scope of each edition, the compliance risks introduced by new AI workload patterns, and the commercial implications of an on-premises release still in progress. For the full analysis, see the Oracle Database 23ai Licensing Guide.

The Three Editions of Oracle Database 23ai

Enterprise Edition (EE) is priced at $47,500 per processor or $950 per Named User Plus. It supports all Oracle Database options and packs, imposes no resource limits, and is required for production deployments that need RAC, Partitioning, Advanced Security, In-Memory, Active Data Guard, or any other paid option. EE is the standard choice for mission-critical production Oracle deployments.

Standard Edition 2 (SE2) is priced at $17,500 per processor or $350 per Named User Plus, and is limited to servers with a maximum of two CPU sockets. SE2 cannot be licensed for any EE option. It cannot run RAC. It supports up to three PDBs per CDB without a Multitenant licence, the same as EE. For smaller workloads that do not require EE options and can operate within SE2's socket constraint, it represents a meaningful cost reduction from EE. However, SE2 deployments require stringent governance: any accidental use of an EE feature on SE2 constitutes a licence violation that is distinct from an options under-licensing issue — it is an edition violation, which Oracle treats as materially more serious.

Oracle Database 23ai Free has no licence fee but is subject to strict constraints: 2 CPUs for foreground processes, 2 GB of RAM, 12 GB of user data, and development or testing use only. It is not licensed for production deployments. Teams that prototype on 23ai Free and leave instances running in production or staging environments create licence exposure that is invisible without a deliberate entitlement review.

Licensing Metrics: How Oracle Counts

The Processor metric counts physical CPU cores, adjusted by Oracle's Core Factor Table. For the majority of enterprise deployments on Intel or AMD x86 hardware, the Core Factor is 0.5, meaning each physical core counts as 0.5 processor licences. A 16-core socket therefore requires 8 processor licences. Oracle's position is that any server on which Oracle software is installed must be fully licensed — not just the servers actively running Oracle at any given moment. This creates a particular risk in VMware environments, where Oracle software can be vMotioned across hosts, and in cloud environments where Oracle may run on physical hosts larger than the virtual machine you provisioned.

Named User Plus (NUP) licences cover identified individuals or devices that access Oracle, whether directly or through an application layer. The minimum NUP per deployment is 25 per Processor (as counted under the Core Factor Table). NUP licensing is cost-effective only where actual, definitively counted users fall well below this minimum. Indirect access through middleware, application servers, or batch processes counts the same as direct user access — the user operating the system that queries Oracle is the Named User, not just the session.

AI Features: Included vs Extra-Cost

Oracle has bundled AI Vector Search, Select AI, and JSON Relational Duality into the base Enterprise Edition and Standard Edition 2 licences without additional charge. This is Oracle's deliberate competitive positioning: by including vector search natively, Oracle aims to retain workloads that might otherwise move to purpose-built AI databases or cloud-native services. For existing EE customers, these capabilities are available without new licence purchases — a genuinely favourable inclusion.

What is not included are the performance-oriented options that AI workloads frequently require. Partitioning for large vector embedding tables ($11,500 per processor), Database In-Memory for analytical acceleration ($23,000 per processor), and Diagnostic Pack for AWR-based performance monitoring ($7,500 per processor) all require separate licences. The risk is that database architects designing AI workloads enable these options as a matter of course — optimising performance without triggering a licensing review. Oracle's LMS audit scripts will detect this usage and quantify it as a compliance gap.

Support Costs and the 8% Annual Increase

Oracle's annual software support fee is set at 22% of the net licence fee in the first year. From the second year onward, Oracle increases support fees by 8% per year. This 8% annual increase is compounded, applies to all licences including options, and is a standard contract term that cannot be changed through routine negotiation. For a customer paying $500,000 in year-one support, the five-year support cost at 8% compounding reaches approximately $2.93 million — compared to a flat-rate projection of $2.5 million. Over a ten-year horizon, the gap between a modelled 8% compounding scenario and a flat-rate assumption represents millions of dollars in unplanned spend.

The only structural way to reduce the impact of the 8% annual increase is to reduce the size of the licence estate on which support fees are paid. A 23ai migration project that consolidates Oracle deployments and reduces total processor licence count delivers compounding savings both in perpetual licence fees and in the support base on which increases compound annually.

Cloud Licensing Nuances for 23ai

On Oracle Cloud Infrastructure (OCI), customers can deploy 23ai under BYOL (applying existing perpetual licences) or under License Included pricing. OCI's OCPU metric aligns with Oracle's processor metric, making BYOL straightforward for customers with adequate perpetual entitlements. For AWS, Azure, and Google Cloud deployments outside Oracle's co-location services, Oracle's Cloud Licensing Policy requires that all vCPUs on the physical host be licensed unless approved hard partitioning is in use — a requirement that standard cloud instance types do not satisfy. Customers running Oracle 23ai on standard EC2, Azure VM, or GCP compute instances without addressing this rule face a significant potential compliance gap.

Key Compliance Rules to Enforce

For any 23ai deployment, the following compliance rules should be part of your governance framework. First, never create a fourth PDB in a CDB without confirming a Multitenant option licence is in place. Second, never enable Oracle Enterprise Manager management packs (Diagnostic Pack, Tuning Pack) on databases where those packs are not licenced. Third, never assume that features available in the 23ai Free edition are licenced for production use — they are not. Fourth, conduct quarterly licence reviews using Oracle's DBA_FEATURE_USAGE_STATISTICS view to detect any option activation before an Oracle audit surfaces it. Fifth, do not run Oracle software on AWS or Azure standard instances without addressing Oracle's Cloud Licensing Policy.

Redress Compliance provides independent Oracle Database licensing advisory across assessment, audit defence, and negotiation. Contact our Oracle team to discuss your 23ai licensing position.