Oracle Database 23ai Licensing Guide

What Is Oracle Database 23ai?

Oracle Database 23ai, released in May 2024, is the successor to Oracle Database 19c and 21c and the long-term support release for this generation of the Oracle database engine. The "ai" suffix signals Oracle's strategic intent: to position 23ai as the natural platform for enterprises running AI-powered workloads on their existing Oracle estate. Oracle states that more than 300 new features are included in 23ai, with AI Vector Search being the most prominent.

For licensing purposes, 23ai is not a new product. It runs on the same licensing framework as previous Oracle Database releases — the same processor and Named User Plus (NUP) metrics, the same edition hierarchy, the same options and packs structure, and the same Oracle support model. What has changed is the set of capabilities available within each edition, and the practical compliance risks introduced by new feature interaction with the options and packs regime.

Understanding which 23ai features are included in your existing licence, which require new option purchases, and which create inadvertent compliance exposure is the central challenge for procurement and licensing teams working with this release.

Editions and Base Pricing

Oracle Database 23ai ships in three primary on-premises editions. Each edition has a different capability scope and a different price point, and the choice of edition determines which options can be added.

Enterprise Edition (EE)

Enterprise Edition is the flagship edition and the only one that supports the full range of Oracle Database options. The list price is $47,500 per processor or $950 per Named User Plus. Enterprise Edition removes all resource constraints — there is no cap on CPU cores, memory, or storage — making it the required choice for production workloads, mission-critical systems, and any deployment where performance or high availability matters. Enterprise Edition is also the only edition eligible for Real Application Clusters (RAC), Partitioning, Advanced Security, In-Memory, and other paid options.

Standard Edition 2 (SE2)

Standard Edition 2 is priced at $17,500 per processor or $350 per Named User Plus. SE2 is limited to servers with a maximum of two sockets and does not support any of the paid EE options. It is not licensed for use with RAC (though Oracle's own Oracle RAC One Node is available as a separate product). SE2 can host up to three PDBs without a multitenant licence, the same as Enterprise Edition. For smaller, less complex workloads where EE options are not needed, SE2 can deliver significant cost savings — but organisations must rigorously govern feature usage to avoid inadvertent EE option activation.

Oracle Database 23ai Free

Oracle offers a free edition, Oracle Database 23ai Free, available for download and use without a licence fee. The free edition is subject to hard resource limits: a maximum of 2 CPUs for foreground processes, 2 GB of RAM (combined SGA and PGA), and 12 GB of user data. Critically, the free edition is not licensed for production use, revenue-generating applications, or any business-critical workload. It is appropriate for development, testing, and educational use only. Deploying 23ai Free in a production environment — even temporarily — constitutes a licensing breach.

Licensing Metrics: Processor vs Named User Plus

Oracle Database is licensed using one of two mutually exclusive metrics on any given installation: Processor or Named User Plus. You cannot mix metrics for the same Oracle Database deployment.

Processor Licensing

Under the Processor metric, you licence each physical processor (CPU socket) on which Oracle Database runs, applying Oracle's Core Factor Table. The Core Factor varies by chip architecture. For Intel and AMD x86 processors, the factor is currently 0.5, meaning a server with two sockets each carrying a 16-core chip has 32 physical cores, which multiplied by 0.5 gives 16 Processor licences required. For SPARC and other architectures, different factors apply. Processor licensing is most appropriate where the number of actual users is large, unknown, or unlimited.

One critical rule: if Oracle Database software is installed on a server — even if it is not actively running — you may be required to licence all the processors on that server under certain Oracle audit interpretations. Oracle's position is that the software must be licensed on any server where it is installed and accessible. Organisations should be especially careful about standby databases, Oracle software on VMware or other hypervisors, and software distributed across containerised infrastructure.

Named User Plus (NUP) Licensing

NUP licences cover individual users or devices that access the Oracle Database, directly or indirectly. "Indirect" access matters: if your application tier queries Oracle on behalf of users, those users still count as Named Users. For Enterprise Edition, there is a minimum of 25 NUP licences per Processor. If a server counts as 4 Processors, you need at least 100 NUP licences regardless of your actual user count. NUP licensing is advantageous only where user counts are low, definitively counted, and well below the 25-per-processor minimum floor. Failing to count indirect users is one of the most common audit findings Oracle raises against enterprise customers.

AI Features: What Is Included vs. What Costs Extra

Oracle Database 23ai's most prominent new capabilities are clustered around AI and machine learning. Understanding which of these are included in your base licence and which trigger additional costs is essential before planning any AI workload deployment.

AI Vector Search — Included at No Additional Cost

AI Vector Search is included in both Enterprise Edition and Standard Edition 2 at no additional licence cost. This is Oracle's strategic choice: by bundling vector search natively, Oracle aims to capture AI workloads that might otherwise move to purpose-built vector databases or cloud-native AI services. AI Vector Search enables the database to store and query vector embeddings — numerical representations of text, images, and other unstructured content — making it possible to run semantic similarity searches directly within Oracle without moving data to an external system. For customers already running Enterprise Edition, this capability is available without new licence purchases.

Select AI — Included in EE

Select AI translates natural language prompts directly into SQL queries using a connected large language model. Like AI Vector Search, this feature is available within Enterprise Edition without additional licensing. Select AI requires connectivity to an LLM provider (Oracle's own Generative AI Service on OCI, or third-party models such as OpenAI), and the costs of those services are separate from the Oracle Database licence.

JSON Relational Duality — Included

JSON Relational Duality allows the same data to be accessed as both relational tables and JSON documents simultaneously, without duplication. This is included in EE and SE2 at no additional cost and represents a significant architectural capability for applications that need to support both JSON APIs and relational queries against a single data store.

Features That Still Require Separate Option Licences

The introduction of AI features does not alter Oracle's long-standing options and packs framework. Options such as Partitioning, RAC, Advanced Security, In-Memory, Diagnostic Pack, and Tuning Pack continue to require separate licence purchases. The risk in 23ai is that some AI workloads may inadvertently activate licensed options — for example, partitioned tables used to manage large vector embedding stores, or In-Memory column store activation to accelerate analytical queries over vector data. Customers must ensure their AI workload architecture does not trigger option usage without the corresponding licences.

Database Options and Packs

Oracle Database Enterprise Edition options are extra-cost features that extend the database's capabilities in specific areas. Each option must be separately purchased and must be licensed on every processor where the option is installed or in use. Options carry the same annual support fee as the base database — currently structured to increase by 8% per year — meaning their cost compounds significantly over a multi-year support horizon.

The fully loaded cost of an Enterprise Edition deployment with RAC, Partitioning, Advanced Security, and Database In-Memory can easily exceed $100,000 per processor in perpetual licence fees alone, before annual support is calculated. For a mid-sized deployment of 12 processors, that represents a seven-figure perpetual commitment, with annual support adding a further six-figure recurring cost that increases by 8% each year.

Management Packs

Oracle's management packs — Diagnostic Pack and Tuning Pack — are separate licenced products bundled under Oracle Enterprise Manager. Many organisations activate these packs unknowingly through Oracle Enterprise Manager, OEM Cloud Control, or even third-party monitoring tools that call AWR. Once active, Oracle considers the pack in use, and LMS audit scripts will surface this usage. Organisations running OEM should explicitly disable pack usage for databases where those packs are not licenced.

Multitenant and Container Database Licensing

Oracle Database 23ai's multitenant architecture — Container Databases (CDBs) and Pluggable Databases (PDBs) — introduces one of the most nuanced licensing rules in the Oracle Database framework. Getting this wrong is one of the fastest routes to an unexpected audit finding.

The Free PDB Allowance

Since Oracle Database 19c, Oracle permits up to three user-created PDBs per CDB without requiring a separate Multitenant option licence. This allowance applies to both Enterprise Edition and Standard Edition 2. If your CDB contains only three PDBs (excluding the seed PDB and root CDB, which are always present), you do not need to licence the Multitenant option.

When Multitenant Becomes Mandatory

The moment a fourth user-created PDB is added to a CDB, the Multitenant option must be licenced. The Multitenant option is licenced at $17,500 per processor (or $350 per NUP), and applies to the entire CDB, not to individual PDBs. Once licenced, the CDB can host up to 252 PDBs. Oracle does not enforce a hard technical limit — there is no system-level block preventing you from creating a fourth PDB without the licence. This means the compliance violation is silent unless an audit surfaces it.

Non-Oracle Cloud Environments

For CDBs deployed in non-Oracle cloud environments (AWS, Azure, Google Cloud), the three-PDB free limit applies equally. Oracle restricts multitenant usage in non-Oracle clouds to the same terms as on-premises. Organisations that have migrated Oracle workloads to AWS or Azure and are using multitenant architectures there must ensure they either remain within the three-PDB limit or hold the Multitenant option licence — a point that cloud migration projects frequently overlook.

Cloud Licensing: OCI, AWS, Azure and Google Cloud

Oracle Database 23ai's general availability on-premises (for non-Exadata, non-ODA hardware) has been subject to repeated delays. As of early 2026, 23ai is generally available on Oracle Exadata, Oracle Database Appliance (ODA), and Oracle Cloud Infrastructure (OCI), and is also available through Oracle Database@Azure, Oracle Database@Google Cloud, and Oracle Database@AWS. The general on-premises release for commodity hardware remains pending.

OCI Licensing

On OCI, Oracle Database 23ai is available in two commercial models: Bring Your Own Licence (BYOL) and License Included. Under BYOL, existing on-premises perpetual licences are applied to OCI deployments using Oracle's cloud licence portability rules. Under License Included, the database licence cost is embedded in the OCI consumption price. Customers who have over-licensed on-premises may find BYOL to be more economical; those with tight or insufficient licence positions will need License Included to remain compliant. OCI is the only public cloud where Oracle's Core Factor Table applies in the same way as on-premises — meaning OCPU counts translate directly to processor equivalents.

Non-Oracle Cloud (AWS, Azure, Google Cloud)

In non-Oracle cloud environments, Oracle's Cloud Licensing Policy applies. Oracle counts vCPUs, not physical cores, for licensing purposes in these environments. The standard treatment is: 2 vCPUs = 1 Oracle processor licence (after applying a hard partition exception). However, Oracle requires the use of approved hard partitioning technologies to take advantage of sub-server licensing. Most standard cloud instance types do not constitute approved hard partitions under Oracle's policy. This means customers running Oracle on standard AWS EC2 or Azure VM instances must licence all vCPUs on the physical host if Oracle's default counting methodology applies — a profoundly expensive outcome. This is one of the highest-risk licensing areas Redress Compliance sees in client engagements.

Oracle Database@Azure, @AWS, @Google Cloud

Oracle's co-location services — Database@Azure, Database@AWS, and Database@Google Cloud — place Oracle hardware inside the respective cloud providers' data centres. These deployments are licenced under Oracle's standard on-premises terms, avoiding the cloud licensing policy complications that affect standard EC2 and Azure VM deployments. For enterprises committed to a particular hyperscaler but needing Oracle Database without cloud licensing risk, these dedicated deployment options merit serious evaluation.

Upgrade Path and Licensing Implications

Oracle Database 23ai accepts direct upgrades only from Oracle Database 19c (version 19.3 and higher) and Oracle Database 21c (version 21.3 and higher). Customers running Oracle 12c, 18c, or earlier must first upgrade to a supported source version before migrating to 23ai. This extends the total upgrade timeline and creates an interim period where both versions may be running simultaneously.

Parallel Running and Licence Double-Counting

Running source and target environments in parallel during a migration is a common and operationally necessary practice. However, Oracle's licence terms do not automatically permit parallel running without additional licences. If the source database remains running (even in standby or read-only mode) during the 23ai deployment, those processors typically require separate licences unless you have negotiated specific migration rights. Failing to address parallel running in the migration plan is a frequent source of unexpected compliance exposure.

Consolidation Opportunity

23ai's multitenant architecture creates a genuine opportunity to consolidate multiple standalone databases into a single CDB. Up to three PDBs can be hosted without additional licence cost. Customers who currently run three or more separate Oracle instances on separate servers — each requiring its own processor licence — may be able to consolidate those instances into a single CDB on a single server, significantly reducing the total processor licence count. This consolidation play is one of the most compelling commercial justifications for a 23ai migration and should be modelled before any upgrade project commences.

Support Costs and Annual Increases

Oracle support — Oracle Software Update Licence & Support (SULS), sometimes called CSI or Customer Support Identifier — is priced at 22% of the net licence fee in the first year of purchase. However, Oracle's support fees increase by 8% per year, and this increase compounds annually. This is not a widely publicised figure, but it is a structural cost driver that procurement teams must model when evaluating the total cost of Oracle Database ownership.

The compounding effect is significant. A customer paying $500,000 in year-one support will face support costs of approximately $540,000 in year two, $583,000 in year three, $630,000 in year four, and $680,000 in year five — a cumulative five-year support spend of approximately $2.93 million, compared to a flat-rate projection of $2.5 million. Over a ten-year Oracle relationship, the difference between modelling 8% compounded increases and assuming a flat rate can represent millions of dollars in unbudgeted spend.

ULA and Support Costs

Customers who hold an Oracle Unlimited Licence Agreement (ULA) have their support costs fixed as a lump sum for the duration of the ULA term, regardless of how many additional deployments are made. This is one of the most important financial characteristics of ULA structures: support fees are fixed regardless of deployment volume, so customers must maximise deployment before the ULA certification date — every additional deployment is free and reduces the cost per unit. Customers who fail to maximise deployment squander the primary commercial value of the ULA model.

Audit Risks and Compliance Controls

Oracle's audit programme — conducted by the Oracle LMS (Licence Management Services) team — is one of the most aggressive in enterprise software. Oracle selects audit targets based on a range of indicators, including deployment growth, support renewal value, and intelligence from Oracle sales teams. For customers running 23ai, the primary audit risks are:

• Inadvertent option activation: Features such as Database In-Memory, Diagnostic Pack, and Tuning Pack can be activated through configuration changes, OEM policies, or DBA actions without explicit licensing review. Oracle's audit scripts query DBA_FEATURE_USAGE_STATISTICS and detect even brief or historical usage.
• Multitenant over-deployment: Creating a fourth PDB in a CDB without a Multitenant licence is a common silent violation. Oracle can surface this through LMS scripts or through customer disclosure in audit questionnaires.
• Cloud licensing undercount: Customers who run Oracle on AWS or Azure without approved hard partitioning and who count only their allocated vCPUs — rather than the full host — are significantly under-licensed under Oracle's cloud licensing policy.
• AI workload option creep: As customers deploy AI workloads on 23ai, database architects may configure partitioned tables for vector embedding storage or activate In-Memory for analytical acceleration, triggering option requirements that were not budgeted or licenced.

Internal Compliance Controls

Effective Oracle Database compliance requires a proactive internal control framework. Redress Compliance recommends: quarterly internal licence reviews using Oracle's own LMS scripts (run internally, not shared with Oracle); governance processes that require licensing sign-off for any new database option activation, PDB creation, or cloud deployment; and maintained entitlement records that document all perpetual licences, ULA certifications, and OCS orders. See our guide to conducting internal Oracle licence audits for a step-by-step process.

Negotiation Strategies for 23ai

Oracle's fiscal year ends on 31 May. The Q4 window — March to May — is Oracle's most commercially aggressive period and the point at which Oracle sales teams have the greatest flexibility to offer concessions. Entering a 23ai procurement or renewal negotiation during Q4, with a well-prepared competitive analysis and a clear walkaway position, maximises your leverage.

Key Negotiation Levers

• Cloud migration as leverage: Oracle will negotiate harder to retain workloads they believe are at risk of moving to a competing cloud-native database. A credible evaluation of PostgreSQL, AWS Aurora, or Azure SQL Database strengthens your position significantly.
• ULA vs perpetual: For organisations with significant growth plans, a ULA (Unlimited Licence Agreement) can offer cost certainty — particularly because support fees are fixed for the ULA term regardless of deployment growth. Model the ULA break-even against your projected deployment trajectory before entering negotiations.
• Support fee cap negotiation: While Oracle's 8% annual support increase is standard, experienced advisors have secured contractual caps on support fee increases for specific contract structures. This is not a standard Oracle commercial offer but can be achieved with the right leverage and preparation.
• Options bundling: If you need multiple options (e.g., RAC + Partitioning + Advanced Security), negotiating a bundled discount is more effective than addressing each option separately. Oracle's list prices for options are significantly discountable when the total contract value justifies it.

What Not to Do

Never share your internal Oracle compliance data with Oracle sales or LMS teams during a commercial negotiation. Once you disclose potential gaps in your licence position, that information becomes an audit finding regardless of the commercial context in which it was shared. All compliance analysis should be conducted with independent advisors under legal privilege before any Oracle negotiation commences. Never deploy Oracle software before the licence is in place — even for proof-of-concept work, Oracle's terms can be applied retroactively.

How Redress Compliance Helps

Redress Compliance specialises exclusively in enterprise software licensing advisory, working buyer-side only. Our Oracle practice has supported more than 500 Oracle licensing engagements over 20 years, across database, middleware, applications, and Java. For Oracle Database 23ai specifically, we offer:

• 23ai Licensing Assessment: A structured review of your planned 23ai deployment against your existing licence entitlements, identifying gaps and optimisation opportunities before deployment begins.
• Upgrade Migration Licensing Review: Analysis of parallel running requirements, consolidation opportunities, and cloud licensing implications for your specific migration path.
• Oracle Audit Defence: If Oracle has initiated an audit, we provide independent analysis, counter-measurement support, and negotiation advisory to minimise your exposure. See our Oracle audit defence services.
• ULA and PULA Strategy: Structuring and negotiating Oracle ULA and PULA agreements to maximise deployment value and protect your long-term commercial position.
• Ongoing Oracle Licence Management: Quarterly reviews, entitlement tracking, and governance support to maintain continuous compliance without over-investment.